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

Memory Leak #52

Open
rgasparfin opened this issue Aug 20, 2014 · 4 comments
Open

Memory Leak #52

rgasparfin opened this issue Aug 20, 2014 · 4 comments

Comments

@rgasparfin
Copy link

This plugin have a memory leak.
You can confirm it with chrome task manager for example.
Memory just keep increasing...

@r3verser
Copy link

Yeah, got 4 timers on page, after few hours chrome process eats ~1gb of ram. This leak present i think in all versions of script, cos i have 1.8 and update it to 2. All the same. Need to move to another plugin...

@ghost
Copy link

ghost commented Sep 19, 2014

Same issue here. I've been spending 2 days to debug my JavaScript application and just figured out it was this plugin. Just open http://keith-wood.name/countdown.html in chrome and watch the memory increasing on the task manager.

@interleaver
Copy link

It's a bug in Chrome: https://code.google.com/p/chromium/issues/detail?id=120186
As a workaround you can set $.noRequestAnimationFrame to true before the plugin.

@jeremyhaile
Copy link

@interleaver what are the downsides of disabling requestAnimationFrame? It then falls back to setInterval - is that more CPU intensive?

I'm currently experiencing extremely high CPU usage from this plugin, and I noticed it's from a version prior to requestAnimationFrame being used. So I'm upgrading to the latest, but now I'm worried about the memory leak.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants