mimo Posted August 17, 2017 Report Share Posted August 17, 2017 Since my update to firefox 55, I'm facing a strange bug: each time i start a 0ad game, all my firefox tabs become empty, even when reloading. Reopening a new tab works though. It could be a bug with firefox55, but no other application apart 0ad give me that problem. Anybody facing the same problem? I've 2 pc with kubuntu 17.04 and both have it. Quote Link to comment Share on other sites More sharing options...
fatherbushido Posted August 17, 2017 Report Share Posted August 17, 2017 Have you some firefox extensions? Quote Link to comment Share on other sites More sharing options...
feneur Posted August 17, 2017 Report Share Posted August 17, 2017 IIRC SpiderMonkey can either be system-wide or specific to 0 A.D. could it be that you are using the former and that somehow affects things? I would assume not as that would have been more logical if you always had the issue, than if it just has begun. SpiderMonkey is all that 0 A.D. and FireFox has got in common though, right? 1 Quote Link to comment Share on other sites More sharing options...
mimo Posted August 17, 2017 Author Report Share Posted August 17, 2017 20 minutes ago, fatherbushido said: Have you some firefox extensions? I had disabled them, with still the same problem. Quote Link to comment Share on other sites More sharing options...
mimo Posted August 17, 2017 Author Report Share Posted August 17, 2017 20 minutes ago, feneur said: IIRC SpiderMonkey can either be system-wide or specific to 0 A.D. could it be that you are using the former and that somehow affects things? I would assume not as that would have been more logical if you always had the issue, than if it just has begun. SpiderMonkey is all that 0 A.D. and FireFox has got in common though, right? As i was not sure how it is set when i compile it, i've installed the 0ad A22 package from ppa:wfg/0ad and have the same problem. Quote Link to comment Share on other sites More sharing options...
mimo Posted August 18, 2017 Author Report Share Posted August 18, 2017 After some investigation, the problem is linked to the new tab multithreading of firefox, actived by default on my kubuntu with firefox 55. I switched "browser.tabs.remote.autostart.2" to false in about:config and that cured the problem (although loosing the multi-threading). But still i don't understand why this only happened when starting Oad. I'd be interested if others are also running firefox 55: what are your values of browser.tabs.remote.autostart and browser.tabs.remote.autostart.2 in about:config? and do you see the same problem when multithread is activated? 1 Quote Link to comment Share on other sites More sharing options...
fatherbushido Posted August 18, 2017 Report Share Posted August 18, 2017 I am running it too. I will check the value. edit: browser.tabs.remote.autostart -> false (default) browser.tabs.remote.autostart2 -> true (modified, that's perhaps a debian patch) Quote Link to comment Share on other sites More sharing options...
mimo Posted August 18, 2017 Author Report Share Posted August 18, 2017 I had the same values, and you have no problems when starting 0ad while firefox was open with some tabs? should then be something in my system Quote Link to comment Share on other sites More sharing options...
Guest Dunedan Posted August 19, 2017 Report Share Posted August 19, 2017 Got the same problem as well with Firefox 55 under Debian. Happens with Alpha 21 directly from the Debian archive as well as with a manually compiled Alpha 22, which should use mozjs shipped with 0ad. So I'm quite puzzled where the relation is coming from. Quote Link to comment Share on other sites More sharing options...
fatherbushido Posted August 19, 2017 Report Share Posted August 19, 2017 I have a flashing black screen when opening firefox (with our without 0ad) Quote Link to comment Share on other sites More sharing options...
mimo Posted August 21, 2017 Author Report Share Posted August 21, 2017 Thanks Dunedan, at least i'm not alone with that bug PS An additionnal info, the problem does not happen with non-visual replays Quote Link to comment Share on other sites More sharing options...
Dunedan Posted September 9, 2017 Report Share Posted September 9, 2017 Just wanted to point out that this problem went away for me without touching 0ad. So I believe some updated Debian package fixed it. Quote Link to comment Share on other sites More sharing options...
Dunedan Posted September 9, 2017 Report Share Posted September 9, 2017 Ok, that was to early. The problem appeared back again, but this time I noticed that it's not related to 0ad at all. Apparently that problem appears whenever compositing for my DE gets enabled or disabled. As running 0ad disables it, it looked like it is related to 0ad, while it is not. For somebody running with KDE it should be fairly simply to check: Start Firefox and open some page, switch compositing with CTRL + Shift + F12 and you should see blank pages in Firefox. Quote Link to comment Share on other sites More sharing options...
mimo Posted October 3, 2017 Author Report Share Posted October 3, 2017 Seems to be fixed with firefox 56 update! 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.