Closed
Bug 883744
Opened 11 years ago
Closed 11 years ago
[A/V] Crash occur in music application (pthread_mutex_lock | android::OmxDecoder::ReleaseMediaResources())
Categories
(Firefox OS Graveyard :: General, defect, P1)
Tracking
(blocking-b2g:leo+, firefox22 wontfix, firefox23 wontfix, firefox24 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 wontfix, b2g-v1.1hd fixed)
People
(Reporter: leo.bugzilla.gecko, Assigned: sotaro)
Details
(Keywords: crash, Whiteboard: [b2g-crash])
Crash Data
Attachments
(5 files, 1 obsolete file)
Precondition : put some music files in SD card. STR 1. start music app 2. select icon to repeat all music 3. push next music button several times. Then crash occur 100%.
Comment 1•11 years ago
|
||
We need two things to make this actionable: 1. The music files in question - can we get access to them? 2. A crash report ID [2] can be found by getting the crash to happen, connecting to wifi, and waiting for the report to be submitted. Upon submission, follow the steps here - https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Getting_crashes_off_the_Device to get your crash report ID.
Updated•11 years ago
|
Reporter | ||
Comment 2•11 years ago
|
||
Flags: needinfo?(leo.bugzilla.gecko)
Reporter | ||
Comment 3•11 years ago
|
||
Reporter | ||
Comment 4•11 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #1) > We need two things to make this actionable: > > 1. The music files in question - can we get access to them? > 2. A crash report ID > > [2] can be found by getting the crash to happen, connecting to wifi, and > waiting for the report to be submitted. Upon submission, follow the steps > here - > https://wiki.mozilla.org/B2G/QA/ > Tips_And_Tricks#Getting_crashes_off_the_Device to get your crash report ID. I cannot report crash. It's connected by WIFI and Crash report setting is set to "Always send a report" However every crashes leaved in minidump directory. I attached one.
Comment 5•11 years ago
|
||
(In reply to leo.bugzilla.gecko from comment #4) > (In reply to Jason Smith [:jsmith] from comment #1) > > We need two things to make this actionable: > > > > 1. The music files in question - can we get access to them? > > 2. A crash report ID > > > > [2] can be found by getting the crash to happen, connecting to wifi, and > > waiting for the report to be submitted. Upon submission, follow the steps > > here - > > https://wiki.mozilla.org/B2G/QA/ > > Tips_And_Tricks#Getting_crashes_off_the_Device to get your crash report ID. > > I cannot report crash. It's connected by WIFI and Crash report setting is > set to "Always send a report" > However every crashes leaved in minidump directory. > > I attached one. I'm talking about a crash report ID. When you crash, a crash report gets queued to get sent to Socorro. After being connected to wifi, a crash report is then sent to Socorro. After the submission is successful, a crash report ID should appear in the following directory in your phone: /data/b2g/mozilla/Crash Reports/submitted What I'm asking for is the latest crash report ID found in this directory after the crash is submitted.
Reporter | ||
Comment 6•11 years ago
|
||
Reporter | ||
Comment 7•11 years ago
|
||
I don't know why crash report is not uploaded. .dmp and .extra files remained in minidump directory. They doesn't move to Crash Reports/submitted. I upload dump file with call stack.
blocking-b2g: --- → leo?
Updated•11 years ago
|
Crash Signature: [@ pthread_mutex_lock | android::OmxDecoder::ReleaseMediaResources]
[@ pthread_mutex_lock | android::OmxDecoder::ReleaseMediaResources()]
Comment 8•11 years ago
|
||
Example crash report URL - https://crash-stats.mozilla.com/report/index/1c7e534d-4e70-41c1-a8d0-6137e2130615. Only 1 crash.
Updated•11 years ago
|
Keywords: stackwanted
Updated•11 years ago
|
Summary: [A/V] Crash occur in music application → [A/V] Crash occur in music application (pthread_mutex_lock | android::OmxDecoder::ReleaseMediaResources())
Reporter | ||
Updated•11 years ago
|
Priority: -- → P1
Target Milestone: --- → 1.1 QE3 (24jun)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Comment 9•11 years ago
|
||
By applying the patch, I confirmed that the crash did not happen on v1.1 leo.
Assignee | ||
Updated•11 years ago
|
Attachment #764201 -
Flags: review?(chris.double)
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Updated•11 years ago
|
Attachment #764201 -
Flags: review?(chris.double) → review+
Assignee | ||
Comment 10•11 years ago
|
||
Add a header. Carry "chris.double: review+".
Attachment #764201 -
Attachment is obsolete: true
Attachment #764876 -
Flags: review+
Assignee | ||
Comment 11•11 years ago
|
||
Add a header. Carry "chris.double: review+".
Attachment #764879 -
Flags: review+
Updated•11 years ago
|
blocking-b2g: leo? → leo+
Updated•11 years ago
|
status-b2g18:
--- → affected
Assignee | ||
Comment 12•11 years ago
|
||
https://tbpl.mozilla.org/?tree=Try&rev=9f5fdb54d181
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 15•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/a43197217f97
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
status-b2g-v1.1hd:
--- → affected
status-firefox22:
--- → wontfix
status-firefox23:
--- → wontfix
status-firefox24:
--- → fixed
Comment 17•11 years ago
|
||
It seems that we have reproduce this crash since the fix landed on the v1.1. Has the reporter seen the crash with the fix present?
Flags: needinfo?(leo.bugzilla.gecko)
Reporter | ||
Comment 18•11 years ago
|
||
No, after the patch, I have never seen crash by same steps in comment #0. And same call stack attachment #763997 [details], neither.
Flags: needinfo?(leo.bugzilla.gecko)
You need to log in
before you can comment on or make changes to this bug.
Description
•