Frank-Rainer Grahl ha scritto il 24/05/19 alle 16:20:
Gabriel wrote:
Frank-Rainer Grahl ha scritto il 24/05/19 alle 12:54:
Well 2.57 is basically Firefox 60.7 with a few SeaMonkey specific work in
progress fixes. Nothing which should bring a mac down. Did you try Firefox
60.7 for comparision. If this also crashes you might report a bug against it
but in any case it will probably either be hardware related or a bug in
macOS. I will try 2.53 on my mini Mac later.
Firefox 60.7 runs flawlessy, I use it without any issue.
The only program that crashed the whole machine so badly is SM 2.53, among
dozens I have and use regularly, after I updated Mojave to 10.14.5
Bummer but I can't reproduce it here. Installed Bills latest build. Runs fine
as far as I see it:
https://imgur.com/a/g9BzpSr
Hi,
I did other tests and now I think the "culprit" is my profile.
First of all, my default boot disk is an external one (cause it's bigger than
the original internal HD), so I installed SM 2.49.4 - 2.53 - 2.57 on the
internal HDD and started the iMac with only that disk. Then I did a complete
Mojave 10.14.5 installation.
So with a new profile I ran all 3 SM versions: they all worked (but in 2.57 the
Mail doesn't, so I deleted it).
BUT when I started SM 2.53 using my original profile, the iMac crashed again
with the same weird effects, the screen goes crazy like if the GPU was faulty.
So the question is: how is it possible that a (damaged) profile can crash
Mojave hard?
And, most important, is there a way to know which file of the profile is
damaged?
Thank you :-)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
