3 ms·
It's Debian, it can handle 32 bit and 64 bit applications at the same time, and the package manager makes sure you have all the dependencies. I didn't change l
by ars 1y ago
It's Debian, it can handle 32 bit and 64 bit applications at the same time, and the package manager makes sure you have all the dependencies.
I didn't change libraries, it was a gradual switch where you convert applications to 64 bit - and I didn't think to do Firefox, but it wasn't missing 32 bit libraries.
It was simply a profile that I'd been continuously using since approx 2004, and it was probably too large to fit in 32 memory anymore, or maybe Firefox itself needed more memory and couldn't map it. (The system had a 64 bit kernel, so it wasn't low on RAM), but 32 bit apps are limited to 2/3/4GB.
- capitainenemo 1y agoPossible I suppose. You can restrict firefox memory usage in the config. Perhaps their dynamic allocation was getting confused by what was available on the 64 bit machine? Still. Why would any 32 bit app even try to allocate more than it actually could handle. I dunno. I'm still inclined to think missing libs (or out of date libs) - but hard to say without a bit more detail on the crash. Did anything show up in .xsession-errors / stderr ? Were you able to launch it in a clean profile? Were the crashes visible in about:crashes for the profile when launched in 64 bit? I suppose it doesn't matter too much at this point...
- ars 1y agoSee my reply here: https://news.ycombinator.com/item?id=45173661 https://news.ycombinator.com/item?id=45173661