Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: RangeError Maximum call stack size exceeded #1064

Closed
4 of 15 tasks
jperezr21 opened this issue Nov 20, 2024 · 7 comments · Fixed by #1065
Closed
4 of 15 tasks

[Bug]: RangeError Maximum call stack size exceeded #1064

jperezr21 opened this issue Nov 20, 2024 · 7 comments · Fixed by #1065
Assignees
Labels
bug Something isn't working resolved This issue is resolved

Comments

@jperezr21
Copy link

Which variants of Embla Carousel are you using?

  • embla-carousel (Core)
  • embla-carousel-react
  • embla-carousel-vue
  • embla-carousel-svelte
  • embla-carousel-autoplay
  • embla-carousel-auto-scroll
  • embla-carousel-solid
  • embla-carousel-auto-height
  • embla-carousel-class-names
  • embla-carousel-fade
  • embla-carousel-docs (Documentation)
  • embla-carousel-docs (Generator)

Steps to reproduce

Was not able to reproduce.

Expected Behavior

No error.

Additional Context

Started happening after upgrading from 8.3.1 to 8.4.0.

The issue is happening in updateAndRemoveAccumulatedTime:
image

Looking at the diff between 8.3.1 and 8.4.0 it seems that this function was introduced in the new release: v8.3.1...v8.4.0#diff-8cdac3333b1ac4c0d5bb15d6b666ca387664c871d960fbce4f43704207715deeR47-R51

What browsers are you seeing the problem on?

Chrome, Safari, Microsoft Edge

Version

8.4.0

CodeSandbox

No response

Before submitting

  • I've made research efforts and searched the documentation
  • I've searched for existing issues
  • I agree to follow this project's Contributing Guidelines for bug reports
@jperezr21 jperezr21 added the bug Something isn't working label Nov 20, 2024
@davidjerleke
Copy link
Owner

@jperezr21 thanks for your bug report. Did this happen in production or when your development watch was running?

@jperezr21
Copy link
Author

In production.

@davidjerleke
Copy link
Owner

@jperezr21 let me know if you find a consistent way of reproducing the problem. Thanks.

@davidjerleke davidjerleke changed the title [Bug]: RangeError Maximum call stack size exceeded. [Bug]: RangeError Maximum call stack size exceeded Nov 20, 2024
davidjerleke added a commit that referenced this issue Nov 20, 2024
davidjerleke added a commit that referenced this issue Nov 20, 2024
davidjerleke added a commit that referenced this issue Nov 20, 2024
[Bug]: RangeError Maximum call stack size exceeded
@davidjerleke davidjerleke added the resolved This issue is resolved label Nov 20, 2024
@jperezr21
Copy link
Author

Thank you @davidjerleke!

@davidjerleke
Copy link
Owner

@jperezr21 a bug fix has been released in v8.5.1. Try upgrading and let me know if the problem goes away.

@jperezr21
Copy link
Author

@davidjerleke problem went away. Thank you!

@davidjerleke
Copy link
Owner

@jperezr21 that's good to hear. Thanks for letting me know 👍.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working resolved This issue is resolved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants