Closed
Bug 777069
Opened 12 years ago
Closed 6 years ago
Make sure child actors can't force parent to crash with Out-of-Memory (OOM) errors
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 777067
blocking-basecamp | - |
People
(Reporter: sicking, Unassigned)
References
Details
For example by sending an array with 2^31 elements.
Updated•12 years ago
|
Summary: Make sure child actors can't crash parent process through OOP → Make sure child actors can't force parent to crash with Out-of-Memory (OOM) errors
We should specifically focus this on maliciously-crafted IPC messages triggering OOM only in the parent. On b2g, after bug 768832 it will be impossible for content process allocations to cause the parent to be OOM-killed.
Updated•12 years ago
|
blocking-basecamp: --- → -
Comment 2•6 years ago
|
||
Christoph, would you consider this a dupe of work you are doing and closable?
Flags: needinfo?(cdiehl)
Comment 3•6 years ago
|
||
Basically, yes. There will be component specific follow up bugs where such conditions failed.
Flags: needinfo?(cdiehl)
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•