Closed
Bug 784263
Opened 12 years ago
Closed 12 years ago
Crashed full-screen content process causes b2g process to crash on exit
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cjones, Unassigned)
References
Details
STR (1) Load an OOP app that goes fullscreen (2) Cause the app to crash (if it's Cut the Rope on otoro, it will do this for you) (3) Press HOME to try to exit fullscreen The b2g process crashes on a segfault.
Reporter | ||
Comment 1•12 years ago
|
||
Although, I haven't tested exiting from a fullscreen OOP non-crashed process, so this may be another problem.
Reporter | ||
Comment 2•12 years ago
|
||
OK, that seems to work. So looks like OOP+crashed is the magic sauce.
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Chris Jones [:cjones] [:warhammer] from comment #0) > (2) Cause the app to crash (if it's Cut the Rope on otoro, it will do this > for you) Correction: otoro-ics.
Reporter | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•