Sometimes, after a Firefox crash, the New Session button causes Firefox to appear as though about:blank was displayed, but with nothing in the address bar. It's completely non-responsive. This persists through multiple kills and restarts. The bugged sessionstore.js produces this every time I start Firefox. It does not work if I move it over to my Ubuntu install, but that might also be a differing set of extensions, I'll check it on my clean Firefox profile once I've finished this (and hence can close Firefox). Reproducible: Always Steps to Reproduce: 1. Close Firefox. 2. Place the attached sessionstore.js.bugged in ~/mozilla/firefox/<profile>/ as sessionstore.js. 3. Start Firefox. Actual Results: Clicking either New Session or Restore Session causes Firefox to hang at a blank page. Expected Results: New Session should bring up the start page. Restore Session should Installed extensions/plugins: Flash 9.0.31.0 Java 1.5.0.10
Created attachment 113035 [details] Bugged sessionstore.js that produces the issue
Looks like it's one of the extensions.
No, not just one of the extensions. It's some kind of weird synergy, which might mean it's back on Firefox itself. If I disable Nuke Anything Enhanced, DOM Inspector, Copy Plain Text, or Adblock Plus & Filterset.G, the problem goes away. Once I re-enable them, the very first start won't trigger it, but the second will (if you restore the bugged sessionstore.js both times). Anybody have a suggestion on what to try next? I'm out of ideas. Oh, I just noticed that my initial comments weren't complete for some reason (probably user error). Here's what went missing: Expected: Start New Session should bring up the start page. Restore Session should load http://www.whereswaldo.com/. Plugins: Flash 9.0.31.0 Java 1.5.0.10 Extensions: Adblock Filterset.G Updater Adblock Plus 0.7.2.4 Control de Scripts 0.5.0.1 Copy Plain Text 0.3.3 DOM Inspector 1.8.1.2 Flashblock 1.5.2 Greasemonkey 0.6.7.20070131.0 JSView 1.2.9 Nuke Anything Enhanced 0.54
Closing as INVALID since it's caused by extensions; not a Gentoo bug.
