Closed Bug 928206 Opened 11 years ago Closed 11 years ago

Killing a content process always sends recording-device-events:shutdown even if recording is not started

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 926289

People

(Reporter: schien, Unassigned)

Details

This bug is found while doing Bug 919149, we need to make sure shutdown never fire if recording is not started.
What's the user impact of this? What's the severity? Is this needed for 1.2 or not?
Blocks: b2g-getusermedia
User cannot notice this because the extra shutdown is filtered by shell.js in bug 919149. This bug is just for cleaning up the shutdown event usage in gecko.
This bug is actually causing by my patch for bug 919149. see http://dxr.mozilla.org/mozilla-central/source/b2g/chrome/content/shell.js#l1314. There is an unwanted ">= 0" comparison.
I'll include the corresponding fix in the patch for bug 926289 for reducing the review burden.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Summary: [Camera] nsDOMCameraControl::StopRecording always sends recording-device-events:shutdown even if recording is not started → Killing a content process always sends recording-device-events:shutdown even if recording is not started
No longer blocks: b2g-getusermedia
You need to log in before you can comment on or make changes to this bug.