Firefox latest version is crashing on mail.google.com in a BgIOThreapool thread
Categories
(Core :: XPCOM, defect)
Tracking
()
People
(Reporter: droslean, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36
Steps to reproduce:
100% fresh installed firefox.
Navigate to mail.google.com. Try to login.
Output logs:
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ExceptionHandler::GenerateDump cloned child 25694
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Actual results:
Firefox crashes
Expected results:
Firefox should continue working.....
| Reporter | ||
Comment 1•3 years ago
|
||
I tried to uninstall firefox and delete the whole ~/.mozilla folder. Then I fresh installed it and tried again but still firefox is crashing.
I tried to upgrade my fedora to 36. Still firefox is crashing.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Could you type about:crashes in your url bar, and paste here a link to one or several of the submitted crash reports that you know are this issue (from the date/time of the crash)?
Also please copy-paste here the content of the graphics section your about:support page.
| Reporter | ||
Comment 3•3 years ago
|
||
| Reporter | ||
Comment 4•3 years ago
|
||
| Reporter | ||
Comment 5•3 years ago
|
||
Hi Nicolas.
Submitted Crash Reports
Report ID Date Submitted
bp-4230e970-b3b8-45c2-959c-e8fdd0220608 6/8/22, 20:45
bp-f7403d49-0fd6-4717-af76-a9ad20220608 6/8/22, 20:45
bp-6221dc72-5abc-4d91-a23d-fd8d10220608 6/8/22, 20:45
bp-8a1d82c7-a19a-406a-9f56-233280220610 6/10/22, 13:50
bp-cb8b883e-46de-4ca9-b3c4-dfeba0220610 6/10/22, 13:50
Graphics section is attached.
Comment 6•3 years ago
|
||
There's no stack for some reason but the crash is consistently happening in a BgIOThreadPool thread.
| Reporter | ||
Comment 7•3 years ago
|
||
I currently switched to google-chrome since it is impossible to use firefox. Please let me know how I can provide more details that will help to resolve this bug.
Comment 8•3 years ago
|
||
The fact the error is consistently happening on a BgIOThreadPool is unfortunately not super useful. The stacks in these crash reports look like they're probably pretty broken. I don't have a concrete idea of what might be breaking here unfortunately without more context from the implementation.
Given that it's been 6 months since this was last looked at (so sorry about that!) is there any chance you'd be able to re-try firefox and see if the issue still occurs? We might be able to get some useful diagnostics and logging if it is.
Comment 9•3 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:nika, since the bug has high severity and recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?
For more information, please visit auto_nag documentation.
| Reporter | ||
Comment 10•3 years ago
|
||
(In reply to Nika Layzell [:nika] (ni? for response) from comment #8)
The fact the error is consistently happening on a BgIOThreadPool is unfortunately not super useful. The stacks in these crash reports look like they're probably pretty broken. I don't have a concrete idea of what might be breaking here unfortunately without more context from the implementation.
Given that it's been 6 months since this was last looked at (so sorry about that!) is there any chance you'd be able to re-try firefox and see if the issue still occurs? We might be able to get some useful diagnostics and logging if it is.
Feel free to close this BUG, since I don't have any other logs to report or help in any way. I have already switched to Google Chrome and I don't plan to investigate further this bug.
Updated•3 years ago
|
Description
•