Argh! I keep finding Firefox using pointers from poisoned memory, only to see them stop reproducing while I try to reduce the repro :/
-
-
Replying to @berendjanwever
this has happened ~3 times this year alone - each time with what appears to be a different root cause... driving me nuts!
1 reply 0 retweets 1 like -
Replying to @berendjanwever
Maybe reducing the repro is causing it to collect garbage at a different (later) time, reducing the likelihood of a crash.
2 replies 0 retweets 2 likes -
Replying to @berendjanwever
I've seen this happen before, due to other objects in the DOM affecting garbage collection
1 reply 0 retweets 1 like -
-
Replying to @berendjanwever
made a tool to enum dom objects related to targeted trigger & then remove 'em systematically. Still only partially helped.
1 reply 0 retweets 0 likes -
Replying to @Laughing_Mantis
Not sure I follow - I would expect a solution would be to force garbage collection more frequently or at specific points?
1 reply 0 retweets 0 likes -
Replying to @berendjanwever @Laughing_Mantis
i.e. by alloc/release a large number of objects? not knowing the FF gc specs, I haven't figured out how to trigger exactly
1 reply 0 retweets 1 like
A bit of debugging suggests "new Uint32Array(0x2000000);" might do the trick, but I have no way to make sure.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.