Open Bug 1227357 Opened 9 years ago Updated 2 years ago

Firefox crash using window fatigue

Categories

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

42 Branch
defect

Tracking

()

UNCONFIRMED

People

(Reporter: qab, Unassigned)

References

Details

(Keywords: crash, csectype-dos, testcase, Whiteboard: [sg:dos])

Attachments

(4 files)

Attached file ff-hang.html
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:

Based on an existing report of a hang: https://bugzilla.mozilla.org/show_bug.cgi?id=1226990

Except this time FF42 crashes instead of hanging.

Run 'ff-hang.html' and press button


Actual results:

After a few minutes of freeze, firefox crashes


Expected results:

No crash
Stacktrace of crash. Note: crash reporter does not open.
Seems like when I tested this again, the crash reporter did open up, odd.

https://crash-stats.mozilla.com/report/index/bp-3397992e-c463-42ef-bf32-3caf32151124
Group: firefox-core-security
Component: Untriaged → DOM
Product: Firefox → Core
Whiteboard: [sg:dos]
I assume this is unexploitable?
It looks like a safe out of memory crash.
Attached image ff-unknown-win.png
(In reply to Andrew McCreight [:mccr8] from comment #6)
> It looks like a safe out of memory crash.

Ah I see. I have a third case (using the same click bug) which results in what seems like a completely empty firefox window (view attached screenshot) could that be indicative of exploitability. Note I cant reproduce it when I have windbg running.
Flags: needinfo?(continuation)
An empty window may just be another sign of running out of memory, or some kind of hang.
Flags: needinfo?(continuation)
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: