Closed Bug 1276539 Opened 5 years ago Closed 3 years ago

Specific webpage script crashes or hangs Firefox

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: admin, Unassigned, NeedInfo)

References

(Blocks 1 open bug, )

Details

(Keywords: hang, reproducible)

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce:

Went to the following webpage - https://tsgess.com/lawson/portal/


Actual results:

Firefox crashed.


Expected results:

Should not crash? Chrome handles the webpage fine, it doesn't load but you can close the webpage without a crash.
No crash here, just Firefox hangs and still sucks all available RAM.

Post some URLs of these crashlog reports from about:crashes
Blocks: eviltraps
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(admin)
Keywords: hang, reproducible
Version: 46 Branch → unspecified
No crashlog is produced. I left it for a while and I got this - https://i.gyazo.com/453dab83f9a9ccccdd63f723f916c52a.png

Looks like the following script causes the issue - https://tsgess.com/lawson/portal/objects/PortalConfig.js
The offending URL crashed Firefox 46.0.1 Win32 for me after a few minutes. Unfortunately, the crash reporter did not produce a crash report.
Flags: needinfo?(admin)
Summary: Specific Webpage Script Crashes Firefox → Specific webpage script crashes or hangs Firefox
Component: Untriaged → DOM
Product: Firefox → Core
This looks to me like it is due to loading a synchronous script. Either way I can only see that it makes the tab slow. I wasn't able to reproduce it taking all my ram or crashing.
What OS are people using here?
Is this still reproducible?
Flags: needinfo?(admin)
Marking incomplete for now, feel free to reopen if this is still an issue.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.