New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox Nightly invisible w/ Greasemonkey 1.13 beta 5 & 6 #1833

Closed
KobeLAL opened this Issue Nov 20, 2013 · 7 comments

Comments

Projects
None yet
5 participants
@KobeLAL
Copy link

KobeLAL commented Nov 20, 2013

Hello,

i test the two beta Versions (1.13 beta5 and 6). On this two Versions Firefox starts invisible. I see the Firefox.exe in the taskmanager but no Window. Beta 4 works. Im on Nightly 28.

Edit: sry i forget: im on Windows 7 x64.

Thanks

@CHEF-KOCH

This comment has been minimized.

Copy link

CHEF-KOCH commented Nov 27, 2013

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.

@arantius

This comment has been minimized.

Copy link
Collaborator

arantius commented Nov 27, 2013

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?

@CHEF-KOCH

This comment has been minimized.

Copy link

CHEF-KOCH commented Nov 28, 2013

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:
-> I'm under Windows 7 SP1 x64

  • Install latest nightly ff
  • Open 20 or more taps in firefox
  • Install beta 6 (enabled beta sync in options)
  • Install other plugins/extensions too (plays no role which ones)
  • Install 15 scripts from userscripts
  • Close and try to re-open Firefox -> Taskmanager shows you firefox.exe but nothing is visible

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.

Ventero added a commit to Ventero/greasemonkey that referenced this issue Dec 18, 2013

@Ventero

This comment has been minimized.

Copy link
Contributor

Ventero commented 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 Array#slice and Array#splice), which caused an infinite loop in removeEnqueuedPath when a DB file was successfully deleted during startup.

Ventero@f2611f7 should fix this bug.

Thanks to Stealth in the #greasemonkey IRC channel for spending 2 hours helping me hunt down this bug!

@mt20

This comment has been minimized.

Copy link

mt20 commented Jan 4, 2014

Thank you, Ventero, and Stealth, for allowing me to finally upgrade to 1.13. I had 2 versions of a script installed, both of which use the same database, and uninstalled 1, which triggered the infinite loop. 1.12 was unbothered by it.

@arantius

This comment has been minimized.

Copy link
Collaborator

arantius commented Jan 10, 2014

Please try 1.14beta1 if this is still happening for you:
https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/versions/

@KobeLAL

This comment has been minimized.

Copy link

KobeLAL commented Jan 10, 2014

I test it. And for me it works. Thank you all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment