Back from the Crashing Front
WARNING: the 'heap-allocated' memory reporter does not work for this platform and/or configuration. This means that 'heap-unclassified' is not shown and the 'explicit' tree shows less memory than it should
I'm still having AF crash about once in the course of a 12-hour day — only very occasionally while browsing — mostly when quitting the program after its CPU use has reached 100% and beyond and won't come back down to a normal 0.x-20% anymore. Luckily the steps I've taken (see
earlier post: protect Pin Tabs, lock the
sessionstore.js file in the Profile) have so far allowed me to relaunch it right away without any further damage.
While
Amazon Germany definitely seems to be a guilty party here (so I close its tab right away after using it instead of leaving it open as with the other Amazon platforms), there seems to be other sites that also cause this behaviour. But because these are not “regulars” in my browsing, and because it's impossible to constantly keep an eye on the Activity Monitor for every tab that gets opened, I haven't been able to relate the issue to any one in particular.
The scenario is pretty much the same every time: even after all non-pin tabs are closed, CPU use remains at the same level (yesterday, even around 400%). After I quit AF CPU use surges briefly by 100-150%, then returns to the original excessive value and stays there for (as today) about 75 secs, after which AF crashes. During that period it has occasionally given the pizza wheel and a “(not responding)” in the Activity Monitor.
I thought that Freeing memory at
about:memory after closing tabs (but before quitting) might help. It didn't, but that's when I got the message reported above, in red. Hopefully for the enlightenment of our friendly devs.