Closed
Bug 1027461
Opened 10 years ago
Closed 10 years ago
Running Gaia Unit Tests in B2G Desktop Debug crashes browser on ImportManager assert
Categories
(Firefox OS Graveyard :: GonkIntegration, defect)
Tracking
(tracking-b2g:backlog, b2g-v2.1 fixed)
People
(Reporter: qdot, Assigned: mrbkap)
References
Details
Attachments
(1 file, 1 obsolete file)
4.40 KB,
patch
|
gkrizsanits
:
review+
|
Details | Diff | Splinter Review |
Running Gaia Unit Tests in B2G Desktop built using debug causes the browser to crash on an assert: http://mxr.mozilla.org/mozilla-central/source/content/base/src/ImportManager.cpp#81 Possibly related to Bug 1016705
Assignee | ||
Comment 1•10 years ago
|
||
If we return an error code from OnStartRequest, we will still get a call to OnStopRequest (with our error being propagated). We need to handle that call gracefully.
Attachment #8446835 -
Flags: review?(gkrizsanits)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → mrbkap
Reporter | ||
Comment 2•10 years ago
|
||
Requesting blocking-2.0 because this will affect testing and is a regression.
blocking-b2g: --- → 2.0?
Whiteboard: [systemsfe]
Comment 3•10 years ago
|
||
Comment on attachment 8446835 [details] [diff] [review] Proposed fix Review of attachment 8446835 [details] [diff] [review]: ----------------------------------------------------------------- ::: content/base/src/ImportManager.cpp @@ +269,5 @@ > nsresult aStatus) > { > + if (NS_FAILED(aStatus)) { > + // We failed in OnStartRequest, nothing more to do (we've already > + // dispatched an error event) just return here. Does it always mean that we failed in OnStartRequest and not somewhere else in the process where we haven't dispatched error yet? I would check mStopped to just in case. Thanks for fixing this by the way!
Attachment #8446835 -
Flags: review?(gkrizsanits) → review+
Comment 4•10 years ago
|
||
I don't think this is something we would block on if push came to shove, as we have no proof of user impact & this isn't causing downtime to a test suite that is already stood up in CI.
blocking-b2g: 2.0? → backlog
Whiteboard: [systemsfe]
Assignee | ||
Comment 5•10 years ago
|
||
That was a really good question. Here's a patch that addresses it.
Attachment #8446835 -
Attachment is obsolete: true
Attachment #8448364 -
Flags: review?(gkrizsanits)
Comment 6•10 years ago
|
||
Comment on attachment 8448364 [details] [diff] [review] Patch v2 Review of attachment 8448364 [details] [diff] [review]: ----------------------------------------------------------------- Yeah probably using a specific error is a good idea anyway.
Attachment #8448364 -
Flags: review?(gkrizsanits) → review+
Assignee | ||
Comment 7•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/dd61f96ab348
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/dd61f96ab348
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v2.1:
--- → fixed
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•