Hello

Remember, I use Chrome Canary(dev). I'll switch to beta from time to time to hunt for this bug

You mention "I'll try clearing the cache, but I'm not sure how that will help catching the bug". My reason for that was that if the problem in one window is affecting the results in another window, which isn't supposed to happen, that might be caused by a corruption to the cache (due to a memory management problem, for example). I was trying to determine if refreshing the cache would clear the error, which would indicate that the cached copy was in fact corrupt.

Hmmm...

Alright, I'll try that next time

Basically I meant that since the bug isn't predictable and goes away for long periods of time, there's no way to ascertain if the cache thing helps

You mention that all the tabs show "Aw Snap". Does that happen immediately when one tab crashes, or do you have to start editing in the other ones to make that happen?

@DavideCervone Nope, immediately

the favicons simultaneously slide up to the aw snap thingy

I assume that you have checked the tabs and they really are broken? I don't use Chrome myself very much, so I'm not familiar with how it works, but if the actions in one tab (I may have said "window" before) are affecting another, then something is seriously wrong. Unless Chrome is intentionally blocking all the tabs when one goes bad since it now longer trusts that site. Is that usually what happens with an "Aw Snap" if you have more than one tab open for that site?

@DavideCervone Yeah, they all show aw snap

@DavideCervone Yep, that's Chrome's behaviour

happened on WIkipedia too (probably was one of my scripts)

If something cuts loose Chrome kills the site

OK, then that doesn't indicate cache failure after all. Sorry for the false alarm.

I'm afraid that I am out of ideas about how to analyze this bug.

Me too :/

(I already tried grokking it but nothing worked)

I really think it is a Chrome bug that is triggered by the intense activity involved in the MathJax typesetting, but I don't think MathJax is doing anything illegal per se.

@DavideCervone Yeah, it must be chrome

Maybe there's an issue with wmd.js? Since I never came across this while testing this script

And then, I was banging away at the keyboard like anything, typing random math :)

It might be that if MathJax did things in a different order or something, it might help, but who knows. Yes, wmd could also play a role. It does a lot of string substitutions, so perhaps there is some memory leak there.

Yeah, wmd broke mathjax here as well: meta.chemistry.stackexchange.com/questions/108/…

I'm afraid I'm going to have to throw in the towel on this Chrome issue, and hope Chrome takes care of itself in future versions. I doubt it is worth trying to find a workaround in MathJax with nothing really to go on.