Don Spam's Reckless Son wrote:
> Ant wrote:
>> Hmm, I had one today. Hmm!
>
> I was looking at your list of add-ons:
>
> 1
ubl...@raymondhill.net: 1.16.4.30
> 2
expire-hist...@bonardo.net: 1.2.0
> 3
open...@darktrojan.net: 6.8.6
> 4 {8a6c82a1-f6c9-481a-aae7-c96444c9a754}: 7.1.1
> 5
insp...@mozilla.org: 2.0.19
> 6
mod...@themes.mozilla.org: 2.53.16
>
> I use "1" myself, "5" and "6" are obviously harmless (I use the Default
> theme myself).
> That leaves "2", "3" and "4" (wtf is "4"?)
> You could probably disable "2" for a while and see what happens, but
> comparing your list with Tristan's could also possibly be helpful.
> Disabling "3" would be a problem for you, as for "4" - really, wtf is it?
>
> The way my Seamonkey was generated, I don't have that crash information
> anyway (no about:crashes at all). If it was possible there would have
> been enough of them from when I had 2.53.15.
8a6c82a1-f6c9-481a-aae7-c96444c9a754 appears to be the ID of the PrefBar
extension. That doesn't seem to be available from
<
https://addons.thunderbird.net/seamonkey/>, and I'm not sure where the
official download for it is, but
<
http://prefbar.tuxfamily.org/archive.html> says:
> Please be aware, that PrefBar is no longer maintained! It is not recommend to install any of these versions!
> They most probably don't work well with current versions of SeaMonkey and they won't install at all on Firefox 57 and above!
7.1.1 is the latest version listed, released in 2017 so pretty old. I'm
not sure why it would have suddenly started causing problems without
having updated SeaMonkey, but could be worth seeing if disabling it
stops the crashes. Maybe a configuration change could have triggered
something that wasn't a problem before.
--
Mark.