You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
In commit e11f3ed I forgot to update silent version (HackTimer.silent.min.js) (issue 13) that you used (package.json).
So it was not fixed that time.
Now it is updated (8e2fef9, c06bbc6).
Activity
turuslan commentedon Nov 21, 2015
thank you for reporting.
i will try to find out and fix it.
timotheeg commentedon Nov 26, 2015
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.
Clearing timeout after timeout callback ( #11 (comment) ). Limit and …
turuslan commentedon Dec 3, 2015
Thanks to @timotheeg, there was such a mistake of not deleting unused timeout entries. Commit e11f3ed must fix it.
seiyria commentedon Dec 3, 2015
I'll give this a try sometime later and see if it's still causing problems. If so, I'll let you know. Thanks!
turuslan commentedon Jan 18, 2016
In commit e11f3ed I forgot to update silent version (HackTimer.silent.min.js) (issue 13) that you used (package.json).
So it was not fixed that time.
Now it is updated (8e2fef9, c06bbc6).