3 ms·

Here is one of the crash reports: https://crash-stats.mozilla.org/report/index/15999dc2-9465-4592-9ec5-b25e80250908 https://crash-stats.mozilla.org/report/index

by ars 1y ago

Here is one of the crash reports: https://crash-stats.mozilla.org/report/index/15999dc2-9465-4592-9ec5-b25e80250908 https://crash-stats.mozilla.org/report/index/15999dc2-9465-4... (I happened to have an un-subitted one which I just submitted, all the other ones I submitted are older than 6 months and have been purged.) It would crash in random spots, but usually some kind of X, GLX, EGL or similar library. But I don't think it was GLX, etc, because it also didn't save my profile except very very rarely, which was actually a much worse problem!! (This crash is from a long time ago, hence the old Firefox version.)

capitainenemo 1y ago
Is that proprietary nvidia driver stuff in the stack trace?
- ars 1y ago
  Yes, without it YouTube plays at like 5fps. If it matters, that proprietary nvidia stuff is still there with the 64 bit which is rock solid. Also, I tried disabling EGL in the 32 bit with no effect on the crashing.
  - capitainenemo 1y ago
    hm. would be nice to have one of the traces with egl disabled. but I guess this is not really my problem to debug, esp since it's such an edge case (32 bit on 64 bit machine + nvidia blob) and given mozilla is abandoning support anyway.
sfink 1y ago
I understand this might seem unlikely given that it's working fine as 64-bit, but that crash dump makes me want to suggest running a memory tester. It has "Possible bit flips max confidence" of 25%. Ignore the exact percentage, I don't think it means much, but nonzero is atypical and concerning. (Definitely not a proof of anything!) "It would crash in random spots" is another piece of evidence. Some legitimate problems really do show up in a variety of ways, but it's way more common for "real" problems to show up in recognizably similar ways. And having a cluster in graphics stuff can sometimes mean it's triggered by heat or high bus traffic. I'll admit I'm biased: I work at Mozilla, and I have looked at quite a few bugs now where there were good reasons on the reporter's side as to why it couldn't possibly be bad RAM, and yet the symptoms made no sense, and it ended up being bad RAM. Our hardware is surprisingly untrustworthy these days. But I also happen to be working on things where bad RAM problems are likely to show up, so my priors are not your priors.

by ars 1y ago

capitainenemo 1y ago

Is that proprietary nvidia driver stuff in the stack trace?

ars 1y ago
Yes, without it YouTube plays at like 5fps. If it matters, that proprietary nvidia stuff is still there with the 64 bit which is rock solid. Also, I tried disabling EGL in the 32 bit with no effect on the crashing.
- capitainenemo 1y ago
  hm. would be nice to have one of the traces with egl disabled. but I guess this is not really my problem to debug, esp since it's such an edge case (32 bit on 64 bit machine + nvidia blob) and given mozilla is abandoning support anyway.

sfink 1y ago

I understand this might seem unlikely given that it's working fine as 64-bit, but that crash dump makes me want to suggest running a memory tester. It has "Possible bit flips max confidence" of 25%. Ignore the exact percentage, I don't think it means much, but nonzero is atypical and concerning. (Definitely not a proof of anything!) "It would crash in random spots" is another piece of evidence. Some legitimate problems really do show up in a variety of ways, but it's way more common for "real" problems to show up in recognizably similar ways. And having a cluster in graphics stuff can sometimes mean it's triggered by heat or high bus traffic. I'll admit I'm biased: I work at Mozilla, and I have looked at quite a few bugs now where there were good reasons on the reporter's side as to why it couldn't possibly be bad RAM, and yet the symptoms made no sense, and it ended up being bad RAM. Our hardware is surprisingly untrustworthy these days. But I also happen to be working on things where bad RAM problems are likely to show up, so my priors are not your priors.