1365858 - 54.0b8(32bit win): Crash or hangs on http://www.der-postillon.com/

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Tobias Burnus]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170515124824

Steps to reproduce:

If I call http://www.der-postillon.com/ or any subpage, FIREFOX hangs for about one minute before it displays the page.

Going to http://www.der-postillon.com/2017/05/promis-ungeschminkt.html crashes Firefox (no backtrace as the crash reporter claims that no crash-report server has been configured).

That's with uBlock Origin, NoScript, InlineDisposition (WebExtensions), HTTPS Everywhere enabled.

about:support states: "Multiprocess Windows 0/1 (Disabled)"

Comment 1

[Loic]

I can't reproduce the crash with FF53 or 55.

Does it work?

1) in safe mode:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

2) with a fresh profile:
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Comment 2

[Tobias Burnus]

[Hmm, where did my previous comment end up? I believe I saw it after the "Submit", but I no longer see it?!?]

In any case, here the problem occurs only with NoScript enabled - if I disable it, everything is normal. With NoScript, it reliably hangs & crashes as described. [NoScript, 5.0.4, {73a6fe31-595d-460b-a920-fcc0f8843232}.]

Time wise, the problem correlates either with the NoScript 5.0.4 release or with a recent beta (~b6->~b7?). Let me do some more tests.

(The state of "Multiprocess Windows" does not affect it. [Looking forward to WebExt!])

Comment 3

[Tobias Burnus]

Re-testing confirms: Downgrading to NoScript 5.0.3 solves the problem, installing again NoScript 5.0.4 shows this problem. (Except that I didn't get a crash for that site but Firefox simply was hanging. (Windows added a "(Not Responding)" to the title bar.) After a few minutes, I killed Firefox.

I have written the NoScript developer about the - and, hence, I think it makes sense to close this bug.