Frank-Rainer Grahl wrote on 28/05/2019 09:42:
Gabriel wrote:
Frank-Rainer Grahl ha scritto il 26/05/19 alle 11:35:
Gabriel wrote:
I also switched off the hardware acceleration in SM on the iMac but that
didn't help, on or off it's the same.
So: my (big) sessionstore.json + iMac 10.14.5 with AMD R9 390 = crash.
What I'm also wondering is why neither of SM and Mojave create a crash report!
macOS doesn't send the usual crash report after the reboot and the "crashes"
folder in SM is empty.
So what do you thing about all this mess?
My mac mini only has Intel Graphics so if it works with the later versions
chances are I never can reproduce it. I can only guess what causes it. Might be
3 things: Bad hardware, bad driver or a bug in a different macOS component.
There might be a bug or sequence in SeaMonkey session restore or mozilla code
which triggers it for SeaMonkey only.
Overall I am not seeing a spike in crashes with 2.53. Not one for macOS.
https://crash-stats.mozilla.com/topcrashers/?product=SeaMonkey&version=2.53&days=28
So without either a macOS or SeaMonkey crash report not much which can be done
:(
Happy to try the sessionstore.json file.
Hi,
for about 3 weeks I didn't have any more freezing, after starting with a new
sessionstore file and importing bookmarks and tabs (see my message
<[email protected]>).
So now after 1 month the sessionstore file grew from 2 MB up to 30 MB! And I had
a few crashes. I'm wondering if there's some limit in the size of that file.
I disabled the "form and search history" but even if I clear both the visited
page and location bar history, the file doesn't reduce.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
