Firefox 70.0b7 crash on x86_64 Linux when using existing profile
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
People
(Reporter: lutoma, Unassigned)
Details
(Keywords: crash)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0
Steps to reproduce:
Upgrade from Firefox 70.0b6 to Firefox 70.0b7 using an existing profile
Actual results:
Firefox crashes on startup before showing the GUI, logging the following errors in the command line:
[20383, Gecko_IOThread] WARNING: pipe error (52): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
###!!! [Child][MessageChannel::SendAndWait] Error: Channel error: cannot send/recv
###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
(Though I'm not sure these error messages are actually related, since I also occasionally see those when terminating Firefox versions that work).
If I start Firefox 70.0b7 with the -P switch and create a new profile, it doesn't crash, so it seems to be related to my profile.
I restored my ~/.mozilla/firefox folder to its 70.0b6 state from a backup to see if it just got corrupted during the upgrade somehow, but 70.0b7 still fails to start with it. Using 70.0b6 with the same restored profile works, so I don't think the profile is broken per se.
I'm not very knowledgeable about Firefox internals so I'm not sure which log files/… could be helpful in debugging this, but I'm happy to upload more helpful information if someone points me in the right direction.
Comment 1•6 years ago
|
||
Lukas, could you please provide the crash reports? Type about:crashes in the address bar, copy the report ID's and paste them here (more details here: https://support.mozilla.org/en-US/kb/mozillacrashreporter#w_viewing-crash-reports)
Thanks!
Comment 2•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 3•6 years ago
|
||
Closing as Resolved: Incomplete due to no update from the reporter. If anyone can still reproduce this issue, please feel free to reopen the bug.
Thanks!
Description
•