4 ms·
If they made it as far as being able to lose something they were working on, then it's less likely to have been a missing library problem. But I don't know what
by sfink 1y ago
If they made it as far as being able to lose something they were working on, then it's less likely to have been a missing library problem. But I don't know what it was; people do successfully run Firefox on 32-bit Linux.
Firefox does have problems with old profiles, though. I could easily see crud building up there. I don't think Firefox is very good about clearing it out (unless you do the refresh profile thing). You could maybe diagnose it with about:memory, if you were still running that configuration.
- ars 1y agoI tried about:memory, I did not find anything useful. See also my reply here: https://news.ycombinator.com/item?id=45173661 https://news.ycombinator.com/item?id=45173661 (I'm no longer running it, I switched to 64 bit and was VERY happy to no longer have crashes.) I technically could re-install the 32 bit one, and try it, but honestly, I don't really want to!