Open Bug 1551087 Opened 5 years ago Updated 2 years ago

Hanging content processes are not killed

Categories

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

Product:
Core
Component:
DOM: Content Processes
Type:
defect

Tracking

()

People

(Reporter: emilio, Unassigned)

References

Details

If you try reproduce bug 1551065 on Nightly, the only way I fond to have a usable nightly again was restarting.

I think this is supposed to work and the process should get killed after a while... shouldn't it?

The priority flag is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jmathies)

For content there's a five second shutdown timeout that should kick in. We currently don't have other reports like this, maybe this is extension related?

Flags: needinfo?(jmathies)
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.