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
finer control of garbage collection would solve that (i.e. window.CollectGarbage in MSIE), but Firefox doesn't have that
2 replies 0 retweets 0 likes -
Replying to @berendjanwever
can't you compile your own version of Firefox with a custom gc()? Not sure how easy it would be though
1 reply 0 retweets 0 likes -
Replying to @saidelike
I'm looking for a zero maintenance solution; having to build new versions of browsers myself is far from that in my experience.
2 replies 0 retweets 0 likes
I'm not trying to log garbage collection, I'm trying to cause it. AFAICT this extension does not do that.
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.