Firefox 73 crash
Categories
(Toolkit :: Crash Reporting, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox73 | --- | affected |
People
(Reporter: jonas, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
Steps to reproduce:
This is Firefox 73 crash. Unfortunately only the Mac crash protocol exists. During the crash I did not actively use Firefox; it was uploading files to Google Cloud Storage using their website in the background.
Crash logs: https://pastebin.com/DgXuVZbs
Comment 1•5 years ago
|
||
I could not reproduce this crash by the provided steps. I set the (Toolkit) Crash Reporting component in the hope that someone triaging bugs from here will have some feedback on the attached crash log and hopefully help to move things forward.
Thank you for your contribution!
Comment 2•5 years ago
|
||
The priority flag is not set for this bug.
:gsvelto, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 3•5 years ago
|
||
Jonas did the crash occur again? Did Firefox crash reporter show up or did you only see the system crash reporter?
It crashed again a few days ago, see #1618110, although I'm not sure if they're related.
In either case I did not get a Firefox crash reported dialog
Comment 5•5 years ago
|
||
The two crashes are very different but they have something in common: they both happened in macOS code and you were accessing large amounts of data (in one case uploading and in the other downloading multiple files). It is possible that you might have a bad bit in memory and that's causing the crashes, can you test your machine with something like Rember or even better memtest86?
So, I tested with both Rember and memtest86 (using the boot USB stick; ~1h full test) and no issue were found.
Do think this could also be related to swapping? MacOS seems to swap pretty aggressively; it's not uncommon that out of my 8G RAM only 3 are used but at the same time another 5G are swapped out.
Comment 7•5 years ago
|
||
If you get more random crashes while swapping one possibility might be that your main drive is faulty, so when data gets written to it and then back it ends up corrupted. But I would say that's unlikely. Did you get any other crashes besides this one and bug 1618110? Also something I forgot to ask: do you have any kind of anti-virus software installed?
No other crashes so far. I've just recently made the switch back from Chrome to Firefox – actually, only a couple of days before first crash.
SSD is pretty new so the least we can say is that it's unlikely to be broken due to wear and tear.
No anti-virus or similar, just a pretty vanilla developer's Mac setup with no crazy special stuff going on.
Maybe I can run Firefox in some kind of debug mode all the time, if it does not have large performance impact, to be prepared for the next crash?
I'd also be willing to try to reproduce the crashes. From the crash logs, do you have any sort of idea how this could be reproduced? Download or upload large amounts of data? Anything more specific?
Comment 9•5 years ago
|
||
(In reply to Jonas H. from comment #8)
No other crashes so far. I've just recently made the switch back from Chrome to Firefox – actually, only a couple of days before first crash.
SSD is pretty new so the least we can say is that it's unlikely to be broken due to wear and tear.
No anti-virus or similar, just a pretty vanilla developer's Mac setup with no crazy special stuff going on.Maybe I can run Firefox in some kind of debug mode all the time, if it does not have large performance impact, to be prepared for the next crash?
You could try running Firefox beta or even Nightly. Note that you can do that without worrying about the profile: you can have release/beta/nightly installed alongside each other and each one will generate its own profile so as not to step on the others' toes.
What's odd about these crashes is that they seem to be happening outside of Firefox control - which is why you don't see the usual crash reporter dialog.
I'd also be willing to try to reproduce the crashes. From the crash logs, do you have any sort of idea how this could be reproduced? Download or upload large amounts of data? Anything more specific?
Downloading or uploading large amounts of data is a good starting point especially if you could do it using both release and beta.
Comment 10•4 years ago
|
||
Closing as WFM given the lack of activity
Description
•