Closed
Bug 848133
Opened 12 years ago
Closed 12 years ago
wrapper.js in the system app has all sorts of code that tries to work with null and throws exceptions
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
Attachments
(1 file, 1 obsolete file)
709 bytes,
patch
|
fabrice
:
review+
|
Details | Diff | Splinter Review |
Early enough in startup, WindowManager.getDisplayedApp and hence currentAppFrame return null.
Assignee | ||
Comment 1•12 years ago
|
||
I audited the other callsites in this file, and they seem to be ok.
Assignee: nobody → bzbarsky
Attachment #721537 -
Flags: review?(fabrice)
Assignee | ||
Updated•12 years ago
|
Whiteboard: [need review]
Assignee | ||
Comment 2•12 years ago
|
||
Attachment #721537 -
Attachment is obsolete: true
Attachment #721537 -
Flags: review?(fabrice)
Attachment #721538 -
Flags: review?(fabrice)
Comment 3•12 years ago
|
||
Comment on attachment 721538 [details] [diff] [review]
Proposed patch for real
Review of attachment 721538 [details] [diff] [review]:
-----------------------------------------------------------------
Thanks Boris!
Attachment #721538 -
Flags: review?(fabrice) → review+
Comment 4•12 years ago
|
||
pushed on master: https://github.com/mozilla-b2g/gaia/commit/02bfa04be6b4996b2893b5a7a247ef837ac355a8
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•12 years ago
|
||
ahal, how do I find out once this has propagated to the gaia that try uses?
Flags: needinfo?(ahalberstadt)
Whiteboard: [need review]
Comment 6•12 years ago
|
||
(In reply to Boris Zbarsky (:bz) from comment #5)
> ahal, how do I find out once this has propagated to the gaia that try uses?
We have to manually request that the emulator be updated by filing a bug under mozilla.org/Release Engineering.
Unfortunately, this is blocked by bug 843893, so we can't update the emulator's gaia until that bug is fixed.
Flags: needinfo?(ahalberstadt)
You need to log in
before you can comment on or make changes to this bug.
Description
•