Closed Bug 1421915 Opened 7 years ago Closed 4 years ago

Unresponsive script is not detected and makes OS very slow [@ IPCError-browser | ShutDownKill ]

Categories

(Core :: DOM: Content Processes, defect, P3)

57 Branch
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox57 --- affected

People

(Reporter: richard.wiseman, Unassigned)

References

(Blocks 1 open bug)

Details

Crash Data

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171116103757

Steps to reproduce:

Start monitoring the system CPU and RAM.  (I used the command line tool, top.)

Visit https://codepen.io/gaearon/pen/ybbQJX?editors=0010 (which is part of the official React tutorial).

In line 4 of the JavaScript, delete the "() => " from the onClick property.

Watch as the RAM usage of the corresponding Web Content process increases to 100% and the system grinds to a halt.

Kill that process to recover responsiveness.

Crash report 800cefaa-e9c2-41f6-a8b0-447ff0171130 is an example of this happening.


Actual results:

The process consumed most of the RAM and the system ground to a halt.


Expected results:

The "unresponsive script" dialogue should have appeared, giving the opportunity to kill the script by clicking a button.
bp-800cefaa-e9c2-41f6-a8b0-447ff0171130
Status: UNCONFIRMED → RESOLVED
Crash Signature: [@ IPCError-browser | ShutDownKill ]
Closed: 7 years ago
Resolution: --- → DUPLICATE
Kohei Yoshino, do you understand what a [meta] bug is in this forum?

Bug 1421915 is not a duplicate of Bug 1279293. Instead Bug 1421915 can be listed as "blocking" Bug 1279293.

Bug 1421915 - Unresponsive script is not detected and makes OS very slow
Bug 1279293 - [meta] Crash in [@ IPCError-browser | ShutDownKill]
Status: RESOLVED → REOPENED
Has STR: --- → yes
Ever confirmed: true
Resolution: DUPLICATE → ---
Summary: Unresponsive script is not detected and makes OS very slow → Unresponsive script is not detected and makes OS very slow [@ IPCError-browser | ShutDownKill ]
Bug 1279293 doesn't have the meta keyword actually.
Component: Untriaged → IPC
Product: Firefox → Core
Component: IPC → DOM: Content Processes
(In reply to Kohei Yoshino [:kohei] from comment #3)
> Bug 1279293 doesn't have the meta keyword actually.

That doesn't mean that Bug 1279293 is not a META bug.

(In reply to Andrew McCreight [:mccr8] from comment #6) Bug 1279293
> This is a generic signature, so different steps to cause a crash from this
> signature should have separate bugs, blocking this bug.


I've added the meta keyword to Bug 1279293 (IPCError_ShutDownKill).
Priority: -- → P3

Closing because no crashes reported for 12 weeks.

Status: REOPENED → RESOLVED
Closed: 7 years ago4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.