Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Firefox Nightly invisible w/ Greasemonkey 1.13 beta 5 & 6 #1833
I can confirm this behavior. It's also on 28.0a1 with Beta 6, the browser starts but you can't see anything, only taskmanager shows me the Firefox.exe. After you start the browser without any addons (safe mode) and disable all extensions one-by-one Greasemonkey seems the problem.
Set me know if you need some logs.
I just downloaded the latest Aurora ("Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Firefox/27.0" and "Built from http://hg.mozilla.org/releases/mozilla-aurora/rev/56f4f6a8d4d9") and installed Greasemonkey 1.12. It's perfectly visible. Then I updated to the latest Greasemonkey beta (now 1.13beta6). Again everything works as expected.
Then I tried Firefox nightly ("Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Firefox/28.0" and "Built from http://hg.mozilla.org/mozilla-central/rev/6ecf0c4dfcbe"). It still works fine, I was able to navigate to about:support and about:buildconfig to get the exact version data.
Is this only on Windows maybe? Could anyone seeing this happen get the same lines from the same about pages to narrow that down?
Sr, this test under Mac OS does not say anything, because it's on clean profile and without any other scripts/extensions you don't know if it's maybe scripts (engine) related issue from Greasemonkey. I maybe was a bit unclear myself too.
Here are the exactly steps to reproduce it:
Now try to find out what cause this problem, start in safe-mode and try to disable one-by-one addon/extensions, and tada Greasemonkey cause this issue. I think it not only have to do with Greasemonkey only or Windows, I think it's script related, maybe some script and of course Greasemonkey cause this. I think it's not Firefox or Windows related, because all other things addons/extensions working without any problems.
I tried all of this steps now more than once and I can reproduce it. Beta 4 (as reported) seems to work.
Strange think, seems that without anything, only Browser + Greasemonkey it seems to work, but that's why I wrote, it's maybe script (engine) related issue. Or any incompatibility, I don't know.
added a commit
Dec 18, 2013
Turns out this is indeed a Windows only issue, as it can only be triggered by removing a script on Windows while the corresponding DB file is locked. The problem was apparently caused by a typo (or confusion about
Ventero@f2611f7 should fix this bug.
Thanks to Stealth in the #greasemonkey IRC channel for spending 2 hours helping me hunt down this bug!
referenced this issue
Jan 8, 2014
Please try 1.14beta1 if this is still happening for you: