Closed
Bug 792846
Opened 12 years ago
Closed 12 years ago
SystemMessageInternal.js fails if one of the message receiver is closed
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: vingtetun, Assigned: gwagner)
References
Details
(Keywords: regression)
Attachments
(1 file)
4.57 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
If you open the dialer and then close it manually you won't receive calls anymore.
E/GeckoConsole( 105): [JavaScript Error: "NS_ERROR_NOT_INITIALIZED: Component returned failure code: 0xc1f30001 (NS_ERROR_NOT_INITIALIZED) [nsIMessageSender.sendAsyncMessage]" {file: "jar:file:///system/b2g/omni.ja!/components/SystemMessageInternal.js" line: 82}]
This is a regression from bug 777206. Adding a simple try/cacth around the content of the broadcast message fix the issue but it seems like one of the listener of the message should have been removed from the list where it has not been.
Updated•12 years ago
|
blocking-basecamp: ? → +
Keywords: regression
Assignee | ||
Comment 2•12 years ago
|
||
Reporter | ||
Comment 3•12 years ago
|
||
Gregor, do you wait for a review or are you going to do a cleaner fix that relies on unregistering listeners by sending a message when the process is closed / crash.
Assignee | ||
Comment 4•12 years ago
|
||
(In reply to Vivien Nicolas (:vingtetun) from comment #3)
> Gregor, do you wait for a review or are you going to do a cleaner fix that
> relies on unregistering listeners by sending a message when the process is
> closed / crash.
So the problem is that we never unregister any message listeners because of bug 793361. so the only clean solution is bug 777508. philikon is working on it but we might want to use the workaround as well.
Assignee | ||
Updated•12 years ago
|
Attachment #663553 -
Flags: review?(fabrice)
Attachment #663553 -
Flags: review?(21)
Reporter | ||
Comment 5•12 years ago
|
||
Comment on attachment 663553 [details] [diff] [review]
patch
Review of attachment 663553 [details] [diff] [review]:
-----------------------------------------------------------------
I don't like the workaround but I can live with it until there is a proper fix. Can you add a comment in the code explaining that this should be removed once the other bugs lands?
Attachment #663553 -
Flags: review?(21) → review+
Assignee | ||
Updated•12 years ago
|
Attachment #663553 -
Flags: review?(fabrice)
Assignee | ||
Comment 6•12 years ago
|
||
Comment 8•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: in-testsuite?
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•