NoScript/Zotero crash Firefox when accessing DE Wikipedia

[Rainer Klute]

Both NoScript and Zotero have been updated recently and now Firefox crashes (and I mean: crashes) each time when accessing the German Wikipedia, e.g. https://de.wikipedia.org/. Loading a Wikipedia page is completely sufficient to provoke the error, no need to access any Zotero functionality.

This happens only if both add-ons are active. If only one of NoScript or Zotero is active (and all other add-ons being deactivated), I can access the German Wikipedia just fine.

[barbaz]

This addon? - https://www.zotero.org/

What are the associated crash report URL(s) from about:crashes? (If the links don't start with "bp-", first click it to submit the crash report.)

Have you reported this to Zotero as well?

[Rainer Klute]

Here's the last crash I triggered yesterday while testing: https://crash-stats.mozilla.com/report/ ... af31170507

And here's another one I encountered just a few minutes ago. It has nothing to do with the German Wikipedia: https://crash-stats.mozilla.com/report/ ... a551170508

Yes, I also reported this to the Zotero team, please see https://forums.zotero.org/discussion/65 ... 1547746017. In fact, I first reported it to them, but they said they only made a little innocent fix (my words).

[barbaz]

Hmm. Does downgrading NoScript have any effect?

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

[Rainer Klute]

Older versions exhibit the same behaviour; I went back until NoScript 2.9.5.2 and tried them all. However, I assumed that I could replace a newer version by and older one by simply installing the latter.

(I'll report this observation to the corresponding Zotero ticket https://forums.zotero.org/discussion/65 ... 017#latest, too.)

[barbaz]

I assumed that I could replace a newer version by and older one by simply installing the latter.

Correct.

The only other thing I can think of atm is that a Firefox update might have caused the conflict. But the timing of this issue, plus your user-agent string, make that seem unlikely.