Uncached rottentomatoes.com Crashes FireFox 3
Posted: Wed May 06, 2009 4:54 pm
Heading over to http://www.rottentomatoes.com to see the buzz on X-men Origins: Wolverine, I was greeted by a lovely FireFox 3.0.10 crash before anything on the site rendered. After some debugging, it looks like my NoScript 1.9.2.6 is at least partially to blame. Here's what I found out:
1) I don't have rottentomatoes.com in my WhiteList and I'm basically using NoScript default settings.
2) So with rottentomatoes.com being untrusted and thus having scripts/objects blocked, Firefox crashes when trying to load the page.
3) However, with NoScricpt set to "Allow scripts globally", the page loads fine.
4) Once the page's content is cached by the browser (by #3), there are no more crashes even with "Allow scripts globally" disabled (i.e. the page is rendered with NoScript blocking scripts and objects as expected).
5) Even after #4, if you reload the page from the server (I used Shift - Reload Button), FireFox crashes again.
Based on #4 and #5, it seems that NoScript is referencing content that doesn't exist if scripts are disabled. However, once that content is added to the browser's cache, it is "reference-able" by NoScript and thus there's no crash. Crashes make a product look extremely bad, so hopefully this will get addressed soon. Lemme know if you need more info from me.
BTW: Is this the preferred method to report bugs -- posts in this forum? Or is there a formal bug tracker somewhere?
Thanks,
-Foam
1) I don't have rottentomatoes.com in my WhiteList and I'm basically using NoScript default settings.
2) So with rottentomatoes.com being untrusted and thus having scripts/objects blocked, Firefox crashes when trying to load the page.
3) However, with NoScricpt set to "Allow scripts globally", the page loads fine.
4) Once the page's content is cached by the browser (by #3), there are no more crashes even with "Allow scripts globally" disabled (i.e. the page is rendered with NoScript blocking scripts and objects as expected).
5) Even after #4, if you reload the page from the server (I used Shift - Reload Button), FireFox crashes again.
Based on #4 and #5, it seems that NoScript is referencing content that doesn't exist if scripts are disabled. However, once that content is added to the browser's cache, it is "reference-able" by NoScript and thus there's no crash. Crashes make a product look extremely bad, so hopefully this will get addressed soon. Lemme know if you need more info from me.
BTW: Is this the preferred method to report bugs -- posts in this forum? Or is there a formal bug tracker somewhere?
Thanks,
-Foam