Makes me wonder whether one of the comments or answers on that page is crashing the client-side mathjax... there are some possible candidates...
Suggest we (temporarily?) create a second sandbox (not this question because we need it for meta) and trial the likely suspects there, under chrome browser... Update: I created a draft meta question and tried each of the 22 answers, but none of them individually caused a crash. So maybe it's not an issue of bad mathjax/LaTeX code, but client-side resources being stressed?
Went digging into the timeline using firefox (because in chrome it was crashing the tab immediately after displaying the page, which is slightly different behavior than when browsing directly to the question -- now it's displaying correclty in chrome. Hm.) Anyway here's what I see under firefox:
and also this observation about a browser crash: