Do major NoScript updates crash SeaMonkey?

[DIV]

I have installed SeaMonkey version 2.46, with NoScript also installed.

From time to time SeaMonkey crashes. Maybe once per month, on average. This could be caused by many things, including the fact that I typically might have more than 100 tabs opened at the same time.

However, I have noticed that after I relaunch SeaMonkey, when the recovered state is automatically restored with the tabs previously open, one additional tab has often (not sure if "always") been opened too, which is the NoScript website. This seems like it would have to be associated with a NoScript update — otherwise why should it be open (and I didn't have it open)?

So, is it possible that major NoScript updates, which are initiated automatically, could cause SeaMonkey to crash?

I have seen that it is possible to disable display of the Release Notes webpage. However, so far I am presuming that simply displaying a website couldn't cause a crash — unless there was something about the way that the display command is implemented.
I also see that I can turn off automatic updating, but that would seem to create a bigger risk to security. https://noscript.net/faq#qa2_6

Has anybody else come across this problem?
How good is the compatibility with SeaMonkey?

Thanks,
DIV

[barbaz]

From time to time SeaMonkey crashes.

Please go to about:crashes and post here the last few crash report URLs. (if the links don't start with "bp-", first click them to submit them)

However, I have noticed that after I relaunch SeaMonkey, when the recovered state is automatically restored with the tabs previously open, one additional tab has often (not sure if "always") been opened too, which is the NoScript website. This seems like it would have to be associated with a NoScript update — otherwise why should it be open (and I didn't have it open)?

This can also happen if some preferences get reset.

So, is it possible that major NoScript updates, which are initiated automatically, could cause SeaMonkey to crash?

Well let's find out. Try installing an older NoScript, updating it manually, and see if SeaMonkey crashes. Try installing an older NoScript, letting it update automatically, and see if SeaMonkey crashes. See how consistent your results are.

Old NoScript @
https://addons.mozilla.org/addon/noscript/versions / https://addons.mozilla.org/addon/noscript/versions/beta
*or*
https://noscript.net/feed?c=100&t=a

I have seen that it is possible to disable display of the Release Notes webpage. However, so far I am presuming that simply displaying a website couldn't cause a crash — unless there was something about the way that the display command is implemented.

You say the release notes are only displayed after you restart after the crash, correct? Thus, unless your SeaMonkey is like Merlin, displaying the release notes cannot be the cause of your crash.

How good is the compatibility with SeaMonkey?

SeaMonkey is a supported browser. I use NoScript with SeaMonkey as my daily browser and it works well.

[DIV]

Hello, barbaz.

I may be not submitting the details of the SeaMonkey crashes: all of them linked to https://crash-stats.mozilla.com/about/throttling/

I lieu of that information, I was thinking it might be useful to try to see if there is any correlation with my SeaMonkey crash history and the NoScript major update releases. (Of course there needs to be a leeway of a day or two, as I may not be using the browser every day.)

Data below are from typing "about:crashes" into the address bar.
2017-08-24
2017-08-10
2017-07-23
2017-07-22
2017-06-30
2017-06-16
2017-05-26
2017-05-23
2017-05-22
2017-05-21
2017-05-15
2017-04-30
2017-04-28
2017-04-05
2017-04-01
2017-03-30
2017-02-23
2016-07-30
2016-05-13
2016-05-03
2016-04-18
2016-02-28
2016-02-25
2016-02-20
2015-10-07
2015-10-04
2015-10-03
2015-10-01
This seems like more SeaMonkey "crashes" than I can recall noticing. Maybe some are actually just from transient "not responding" events.

I couldn't find release dates in the NoScript version history page.

It may take me a while to try the debugging you suggest. How will I know if an old NoScript version has been automatically updated? Just click the icon at bottom right of the browser window and check the version number?

However, if you're also using SeaMonkey regularly, then I guess it might be that in my case some preferences were reset, as you mentioned. Can you expand on that comment? Is there any way to confirm whether relevant preferences were reset? Maybe based on the preference values, or a timestamp on a certain file?

Thanks,
DIV

[barbaz]

I lieu of that information, I was thinking it might be useful to try to see if there is any correlation with my SeaMonkey crash history and the NoScript major update releases. (Of course there needs to be a leeway of a day or two, as I may not be using the browser every day.)

By that measure, maybe partially related if you're on the dev channel. Definitely not the whole story though. I don't have time to check all the dates, but quite a few of your crashes are too far away from NoScript releases.

I couldn't find release dates in the NoScript version history page.

They're written in small font right under the version number.

How will I know if an old NoScript version has been automatically updated? Just click the icon at bottom right of the browser window and check the version number?

Pretty much. I was thinking you could check the version number in the Add-ons Manager.

However, if you're also using SeaMonkey regularly, then I guess it might be that in my case some preferences were reset, as you mentioned. Can you expand on that comment? Is there any way to confirm whether relevant preferences were reset? Maybe based on the preference values, or a timestamp on a certain file?

When SeaMonkey crashes, before restarting it, look in prefs.js for the value of "noscript.version". It should match the last used NoScript version.

[DIV]

Thank-you for the extra information.

It seems I must be looking at the wrong page for NoScript release history. When I look at https://noscript.net/changelog I still cannot find any dates for the respective versions.

Regards,
DIV

P.S. AFAIK, I'm not on the dev channel for NoScript.

[therube]

I may be not submitting the details of the SeaMonkey crashes: all of them linked to https://crash-stats.mozilla.com/about/throttling/

Continually open the most recent two in new tabs until they "send".
Then post the URLs.

[barbaz]

It seems I must be looking at the wrong page for NoScript release history. When I look at https://noscript.net/changelog

Yep, wrong page, I'm looking at https://addons.mozilla.org/addon/noscript/versions