-
Notifications
You must be signed in to change notification settings - Fork 91
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
excessive memory leaking #11
Comments
thank you for reporting. |
FYI: I reckon it's because the callback map is not cleared on successful setTimeout callback. For setTimeouts, the callback map should be cleared even if clearTimeout is not called explicitly. |
…cycle fake id to 31 bit unsigned integer range, prevent overwriting of active fake id.
Thanks to @timotheeg, there was such a mistake of not deleting unused timeout entries. Commit e11f3ed must fix it. |
I'll give this a try sometime later and see if it's still causing problems. If so, I'll let you know. Thanks! |
In commit e11f3ed I forgot to update silent version (HackTimer.silent.min.js) (issue 13) that you used (package.json). |
over time, if used for a really long time (8-36 hours) this causes a webpage to become incredibly slow. tested with and without on a project and the speed does not drop if hacktimer is not included.
The text was updated successfully, but these errors were encountered: