Regular unpredictable crashing despite multiple reinstalls
Hello dears.
Starting around April 20th, I've been receiving up to eight crashes per day of Firefox. I have uninstalled and reinstalled Firefox at least four times, including downgrading the browser to an older version and 100% wiping ALL Firefox-related data. I do a large amount of web development work using Firefox and often have upwards of eight or nine tabs active showing different web pages or different user interfaces to aid in this work, and when Firefox crashes reloading them all takes up to ten minutes (including time to re-find and re-write what I was working on in the first place).
I am using Lubuntu 17.10 with KDE Plasma installed as the desktop environment. Currently, I am on Firefox 58.0.2, however when the crashing started I was using 59.0.2.
The crash reports which I read regularly cite libc-2.26.so, and from hovering over the red bar under it I get "missing symbol" suggesting that the file is missing, but I have verified the file exists several times in various locations across my system. My frustration with this problem keeps growing each time it crashes because at this point I'm fairly certain I've done everything I can to fix this (except asking other people here for assistance).
Here are the five most recent crash reports:
bp-2aca1316-4fb4-413a-b503-4efa40180430 bp-c7025ada-8359-47fe-9acf-1defb0180430 bp-b3121ac1-d7a9-4ae4-9546-6865d0180430 bp-70d032ed-a1ce-4568-884d-947960180429 bp-570c3ce6-4332-4782-a9a3-53c6e0180428
They all point to the same file, though the way it gets there seems to differ.
If anyone has any recommendations or thoughts on why this is happening and what is causing it, I would be very happy to hear them. This crashing has been causing me an unreasonable amount of stress.
If you need more information about my system other than what has been provided, please ask.
Thank you. ~Xyr
由 cor-el 於 修改
所有回覆 (7)
Video Card Driver Errors : blocked, u'unavailable, disabled
HW_COMPOSITING', u'log': [{u'status': u'blocked', u'message': u'Acceleration blocked by platform', u'type': u'default'}]}, {u'status': u'unavailable', u'description': u'OpenGL Compositing', u'name': u'OPENGL_COMPOSITING', u'log': [{u'status': u'unavailable', Off Main Thread Painting', u'name': u'OMTP', u'log': [{u'status': u'disabled', u'message': u'Disabled by default', u'type': u'default'}]}]} offMainThreadPaintEnabled: False
Suggest update or reinstall your drivers.
Please let us know if this solved your issue or if need further assistance.
Pkshadow said
Suggest update or reinstall your drivers. Please let us know if this solved your issue or if need further assistance.
I did this, and the issue still persists. Latest crash report:
https://crash-stats.mozilla.com/report/index/b4bfcc09-2cdd-41a7-92fd-42f460180501
I notice that you have content processes enabled.
You can create a new profile to test if your current profile is causing the problem.
See "Creating a profile":
- https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
cor-el said
I notice that you have content processes enabled. You can create a new profile to test if your current profile is causing the problem. See "Creating a profile": If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
This solution had no influence on the problem. Firefox crashed after some time with the same type of error. See crash report: https://crash-stats.mozilla.com/report/index/484f8fe5-37fd-4de8-8e26-751c10180502
I would like to note that I did come across some more information though. I had started Firefox using the terminal command "firefox -P" as suggested, and as I started Firefox this way I got some console output up until the crash. This is the output for the entire time I was using Firefox since running the terminal command:
\#\#\#!!! [Parent][MessageChannel] Error: (msgtype=0x150084,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv
\#\#\#!!! [Child][MessageChannel] Error: (msgtype=0x150001,name=PBrowser::Msg_AsyncMessage) Closed channel: cannot send/recv
(/opt/firefox/firefox:4402): dconf-WARNING **: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied
ExceptionHandler::GenerateDump cloned child 5613
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
[Child 4555, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
[Child 4402, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353
Bus error (core dumped)
user@host:~$ Failed to open curl lib from binary, use libcurl.so instead
Whether it is of relevance or not us known, however I've noticed there is a pattern to the crashes. They occur when an an event occurs which involves opening a new window (such as htaccess authentication dialogues, new browsing windows, dev tools), or when changing tab in the developer tools. I've yet to observe any other patterns except those two.
由 Xyrhen 於 修改
This is still a regular problem and I have yet to find a solution.
Latest crash: https://crash-stats.mozilla.com/report/index/c9ba07bc-5f94-461f-b479-25b310180505
由 Xyrhen 於 修改
Due to the lack of support (and Mozilla's evident lack of interest in fixing this problem) I'm not going to pursue or push for answers.
I reinstalled my operating system (to fix a problem which arose when trying to fix this problem). As such, this is no longer an issue and does not need to be bothered with.
My levels of satisfaction regarding my search for a less time-consuming fix are not very high. Thankfully the OS reinstall has fixed this, though I shouldn't have needed to do this at all.
Hi, well it seems you had several answers with in the same day. As well ad not worked through other things could have tried. But since your brought on issue that needed a reinstall I guess it was best then. Sorry us Firefox Volunteer Support could not help you as fast as you wished. Since site was down most of last night being worked on there was no way to answer you further. As well Volunteer Support Contributors are from all over the world so it is not like we have to do this but is on our own time. Glad you fixed your issue.