Tabs always crash on Firefox launched by mozregression
Categories
(Testing :: mozregression, defect)
Tracking
(Not tracked)
People
(Reporter: augustin.trancart, Unassigned)
Details
Attachments
(1 file)
206.38 KB,
image/png
|
Details |
Description
When mozregression launches firefox, all the tabs are in crashed state.
Steps
- install
mozregression
, either from pip or from git master - execute
mozregression
. I've tested
mozregression --launch 2018-01-01
mozregression --launch 2019-01-01
mozregression --launch 2020-02-03 - check the tabs, open new ones, try to refresh
expected
tabs load
actual
On every single tab:
:-( Gah. Your tab just crashed.
Additional info
-
I'm on Kubuntu 20.04, on a X1 Carbon
-
browser console has the following errors
[Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]" nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 759" data: no] L10nRegistry.jsm:759:19
[Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]" nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)" location: "JS frame :: resource:///modules/BrowserGlue.jsm :: _collectStartupConditionsTelemetry :: line 1484" data: no] BrowserGlue.jsm:1484:9
- On linux, pip install -r requirements/all.txt does not currently work, so I had to tweak it (dependency problem between flake8 and pycodestyle, and mozinfo and distro).
Please let me know if you need more info.
Comment 1•4 years ago
|
||
Hi! That's pretty odd. Does a plain Firefox nightly build (tar.gz) downloaded from Mozilla work?
(In reply to Augustin Trancart [:autra] from comment #0)
- On linux, pip install -r requirements/all.txt does not currently work, so I had to tweak it (dependency problem between flake8 and pycodestyle, and mozinfo and distro).
I'm pretty sure these errors are spurious, you can safely ignore them. Actually, the mozinfo<->distro thing is definitely just a bug in mozinfo, I'll file a bug about that.
Comment 2•4 years ago
|
||
(In reply to William Lachance (:wlach) (use needinfo!) from comment #1)
I'm pretty sure these errors are spurious, you can safely ignore them. Actually, the mozinfo<->distro thing is definitely just a bug in mozinfo, I'll file a bug about that.
Reporter | ||
Comment 3•4 years ago
|
||
Hi! That's pretty odd. Does a plain Firefox nightly build (tar.gz) downloaded from Mozilla work?
Yes (tested with fresh profile).
Comment 4•4 years ago
|
||
Unable to reproduce in a new Kubuntu 20.04 64bit VM.
Reporter | ||
Comment 5•4 years ago
•
|
||
That does not suprise me, I can only reproduce on one of my 2 machines. So it's only with some graphic cards at least.
Reporter | ||
Comment 6•4 years ago
•
|
||
And btw, it only bugs in some websites, and BBC is not one of them. You should try with twitter Ian.
Reporter | ||
Comment 7•4 years ago
|
||
Oh I'm sorry I mixed 2 bugs. Please ignore the last 2 comments
Comment 8•4 years ago
|
||
The severity field is not set for this bug.
:wlach, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 9•4 years ago
•
|
||
Per comment 4, this seems to work for others. :autra, please feel free to reopen if you can provide information on how to reproduce.
Comment 10•2 years ago
|
||
I'm also experiencing this issue. Found this bug because I can't use mozregression to run old Fx versions, every tab crashes. Tried the three builds from first comment and all of them are unusable for me.
I just moved from Windows to Linux, maybe my system is missing some old dependencies required by old Fx versions?
I'm using Kernel 5.15.25-1-Manjaro x64, KDE 5.24.2, X11.
Using mozregression, I can say builds from 2020-08-31 or older are unusable for me (all tabs crash instantly), while builds since 2020-09-01 work fine.
Comment 11•2 years ago
|
||
It seems to be bug 1660901. The suggestion made in https://bugzilla.mozilla.org/show_bug.cgi?id=1660901#c22 fixed it for me:
security.sandbox.content.level = 0
Description
•