Closed
Bug 1046341
Opened 10 years ago
Closed 10 years ago
[B2G][Camera][Gecko] Camera initialization failure does not release ownership
Categories
(Firefox OS Graveyard :: Gaia::Camera, defect)
Tracking
(blocking-b2g:1.4+, b2g-v1.3 wontfix, b2g-v1.3T wontfix, b2g-v1.4 fixed, b2g-v2.0 fixed, b2g-v2.1 fixed)
People
(Reporter: aosmond, Assigned: aosmond)
References
Details
Attachments
(2 files, 2 obsolete files)
3.71 KB,
patch
|
aosmond
:
review+
bajaj
:
approval-mozilla-b2g32+
|
Details | Diff | Splinter Review |
4.39 KB,
patch
|
Details | Diff | Splinter Review |
If the camera initialization fails, we do not release the camera ownership, hence subsequent attempts will all fail due to their already being an owner for the camera.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → aosmond
Blocks: camera-events
Status: NEW → ASSIGNED
status-b2g-v1.3:
--- → wontfix
status-b2g-v1.4:
--- → affected
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → affected
Comment 1•10 years ago
|
||
[Blocking Requested - why for this release]: this bug was introduced way back in bug 909542. A weakness in the failure-case tests allowed it to go undetected. Failure to fix could result in the Camera app not being able to access the camera hardware (though, practically, killing the Camera and reopening it would fix the issue).
Blocks: 909542
blocking-b2g: --- → 1.4?
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8465060 -
Flags: review?(mhabicher)
Comment 3•10 years ago
|
||
Comment on attachment 8465060 [details] [diff] [review] bug1046341.patch, v1 Review of attachment 8465060 [details] [diff] [review]: ----------------------------------------------------------------- r+ with comments addressed. Thanks, Andrew! ::: dom/camera/test/test_camera_hardware_init_failure.html @@ +29,5 @@ > > +var tests = [ > + { > + name: "init-failure", > + key: "init-failure", nit: extra whitespace and end of line! @@ +44,5 @@ > + info("Running test: init-failure"); > + navigator.mozCameras.getCamera(whichCamera, initialConfig, onSuccess, onError); > + } > + }, > + { Please add a comment here that explicitly states the 'init-success' test MUST follow the 'init-failure' one.
Attachment #8465060 -
Flags: review?(mhabicher) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Fix nits. try: https://tbpl.mozilla.org/?tree=Try&rev=6c179696751e
Attachment #8465060 -
Attachment is obsolete: true
Attachment #8465109 -
Flags: review+
Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
Comment 6•10 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/4056345284df
Keywords: checkin-needed
Comment 7•10 years ago
|
||
sorry had to backout this change for test failures like https://tbpl.mozilla.org/php/getParsedLog.php?id=44957206&tree=B2g-Inbound
Assignee | ||
Comment 8•10 years ago
|
||
try: https://tbpl.mozilla.org/?tree=Try&rev=b73e4df464ae
Attachment #8465109 -
Attachment is obsolete: true
Attachment #8465601 -
Flags: review+
Assignee | ||
Updated•10 years ago
|
Keywords: checkin-needed
Updated•10 years ago
|
Target Milestone: --- → 2.1 S1 (1aug)
Comment 9•10 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/bc8e33fd7a39
Flags: in-testsuite+
Keywords: checkin-needed
Comment 10•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/bc8e33fd7a39
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 11•10 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/db09e41be6b3 Note that per the recent rule change announced in dev-gaia, 1.4 blockers don't have auto-approval to land on v2.0. Please nominate this patch for b2g32 uplift if you feel that it needs to land there as well. Sorry for the inconvenience :(
status-b2g-v1.3T:
--- → wontfix
Flags: needinfo?(mhabicher)
Comment 12•10 years ago
|
||
Comment on attachment 8465601 [details] [diff] [review] bug1046341.patch, v1.2 NOTE: This flag is now for security issues only. Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): improper failure case handling. User impact if declined: on initialization error, camera hardware may remain open in an undefined state; to be cleared may require, at best, closing the app--at worst, rebooting the phone. Testing completed: automated test (included in patch) was created to catch this error, then code was updated to fix the failing automated test; patch passes on tbpl. Risk to taking this patch (and alternatives if risky): trivial to non-existant. String or UUID changes made by this patch: none.
Attachment #8465601 -
Flags: approval-mozilla-b2g32?
Flags: needinfo?(mhabicher)
Comment 13•10 years ago
|
||
P.S. RyanVM, I pre-emptively checked that the patch applies cleanly to 2.0, and it does, so you should be good to go if/when a=2.0+ arrives.
Comment 14•10 years ago
|
||
Backed out from b2g30 for mochitest crashes. https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/605923bdb9c5 https://tbpl.mozilla.org/php/getParsedLog.php?id=45094180&tree=Mozilla-B2g30-v1.4
Comment 15•10 years ago
|
||
Hmm, I just ran the failing test 1000x locally (by tweaking the test script) and it entirely passes.
Flags: needinfo?(mhabicher)
Comment 16•10 years ago
|
||
Patch for b2g30_v1_4, which is missing a small fix to handle null values from Gonk that was added to 2.0+ in bug 981047.
Comment 17•10 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g30_v1_4/rev/89a8a24a8b1b
Keywords: branch-patch-needed
Updated•10 years ago
|
Attachment #8465601 -
Flags: approval-mozilla-b2g32? → approval-mozilla-b2g32+
You need to log in
before you can comment on or make changes to this bug.
Description
•