Closed
Bug 824049
Opened 12 years ago
Closed 6 years ago
Need to be able get crash reporting for e.me apps
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(blocking-basecamp:-, b2g18+)
People
(Reporter: marcia, Unassigned)
References
Details
As discussed in IRC, this morning - we were discussing expected behavior when an app that is added from e.me crashes. Currently when I crash Facebook I just get a notification that Facebook crashed. nhirata: No, adding the Facebook app from everything.me nhirata ah. nhirata everything.me doesn't run OOP yet marcia nhirata: I see nhirata we should file a bug in regards to that. nhirata I'm not sure what we can do about that. nhirata because of that e.me apps can take down the system nhirata at least that's as far as I understood it
Updated•12 years ago
|
blocking-basecamp: --- → ?
Comment 1•12 years ago
|
||
Marking as basecamp- and b2g18+. This will not stop the release but should be addressed as soon as possible.
blocking-basecamp: ? → +
tracking-b2g18:
--- → +
Updated•12 years ago
|
blocking-basecamp: + → -
Comment 2•11 years ago
|
||
So I think what this comes down to is actually "we need to run e.me apps out of process" - we still get crash reports from them right now, just that it's gecko process crashes, i.e. system reboots in terms of what the user is seeing.
Comment 3•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•