Closed
Bug 1021451
Opened 10 years ago
Closed 9 years ago
WebRTC Chat between FFOS and Desktop Computer Resulted in Graphics Crash - mozalloc_abort(char const*) | NS_DebugBreak | mozilla::ipc::FatalError(char const*, char const*, int, bool) | mozilla::layers::PSharedBufferManagerChild::SendAllocateGrallocBuffer(
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
WORKSFORME
tracking-b2g | backlog |
People
(Reporter: kglazko, Unassigned)
References
Details
(Keywords: crash, Whiteboard: [b2g-crash])
Crash Data
Attachments
(1 file)
(deleted),
text/plain
|
Details |
https://crash-stats.mozilla.com/report/index/ee878ae8-ff06-4375-b578-59bb92140606 Here is the crash report, latest build on Flame.
Comment 4•10 years ago
|
||
I tested WebRTC between master flame and Firefox for Windows. It works correctly without crash.
Comment 5•10 years ago
|
||
(In reply to kglazko from comment #0) > https://crash-stats.mozilla.com/report/index/ee878ae8-ff06-4375-b578- > 59bb92140606 > > Here is the crash report, latest build on Flame. The crash just says that a AllocateGrallocBuffer transaction between SharedBufferManagerParent failed by some reasons.
Reporter | ||
Comment 6•10 years ago
|
||
1.) Start the Web RTC chat on the phone. 2.) Have someone join you on Firefox for Mac on the Computer. 3.) The application crashed and caused an OS restart on my phone. 4.) This is not consistently reproducible, because we tried again after that and it worked fine. However, it might be useful to know that this does happen.
Comment 7•10 years ago
|
||
(In reply to kglazko from comment #6) > 1.) Start the Web RTC chat on the phone. > > 2.) Have someone join you on Firefox for Mac on the Computer. > > 3.) The application crashed and caused an OS restart on my phone. It seems that an actual first crash happened on compositor(b2g process) side and then the transaction failed as in Comment 5. > > 4.) This is not consistently reproducible, because we tried again after that > and it worked fine. However, it might be useful to know that this does > happen.
Comment 9•10 years ago
|
||
(In reply to kglazko from comment #8) > Should I report this bug to someone else then, and if so, who? About graphc, milan, nical and I. About webrtc, Randell Jesup seems correct person to notify.
Updated•10 years ago
|
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
Comment 11•10 years ago
|
||
We need to see if we can reproduce this again. This was an OS restart crash, so we really need to get this fixed.
blocking-b2g: --- → backlog
Crash Signature: [@ mozalloc_abort(char const*) | NS_DebugBreak | mozilla::ipc::FatalError(char const*, char const*, int, bool) | mozilla::layers::PSharedBufferManagerChild::SendAllocateGrallocBuffer(mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> const&, unsigned โฆ
Keywords: crash,
steps-wanted
Summary: Web RTC Chat between FFOS and Desktop Computer Resulted in Graphics Crash → WebRTC Chat between FFOS and Desktop Computer Resulted in Graphics Crash - mozalloc_abort(char const*) | NS_DebugBreak | mozilla::ipc::FatalError(char const*, char const*, int, bool) | mozilla::layers::PSharedBufferManagerChild::SendAllocateGrallocBuffer(
Whiteboard: [b2g-crash]
Updated•10 years ago
|
Severity: normal → critical
Comment 12•10 years ago
|
||
The report says MaybeMagicGrallocBufferHandle deserialing error, which is very strange. I think it will hard to find a solution without a reliable STR. The error only occurs when either: (1). Too much fds in the fdset (2). GraphicBuffer::unflatten fail (3). other internal IPC fail (1) is quite impossible, as GraphicBuffer usually use up to 2 fds, and we can pass 7 now. (2) and (3) need reproducing to debug. I'll try it later to see whether I can reproduce the crash.
Comment 13•10 years ago
|
||
I have been hitting intermittent crashes on the homescreen - yesterday I hit https://crash-stats.mozilla.com/report/index/899a2ae0-43de-4d11-93b0-5f0bd2140609. In the app notes of that crash there is a reference to MaybeMagicGrallocBufferHandle. These crashes seemed to happen very randomly and I have not been able to reproduce them.
![]() |
||
Updated•10 years ago
|
status-b2g-v2.0:
--- → affected
status-b2g-v2.1:
--- → affected
Comment 15•10 years ago
|
||
I encountered this crash on the Flame v2.0 while looking for truncations (connected to data, not wifi, and in Tamil [เฎคเฎฎเฎฟเฎดเฏ] language). Attaching the logcat, sorry it's so large. Repro Steps: 1) Update a Flame to BuildID: 20140630000201 2) Settings > Improve Firefox OS 3) Take a screenshot 4) Tap 'Send Mozilla Feedback', then take a screenshot 5) Tap 'happy', then take a screenshot 6) Continue moving briskly about the 'Improve Firefox OS' settings, taking screenshots Device went from 'Improve Firefox OS' settings page to the animated fox boot screen (splash animation). v2.0 Environmental Variables: Device: Flame v2.0 MOZ ril BuildID: 20140630000201 Gaia: c0c8ad187c0466285f2580531e09f8322996f561 Gecko: d4dc609bcc8a Version: 32.0a2 Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32
Waiting for bug 1038461 to land before asking for retest.
Comment 19•10 years ago
|
||
(In reply to Joshua Mitchell [:Joshua_M] from comment #17) > comment 15 addressed the steps-wanted request Josh - Do we know if comment 15 can be consistently reproducible to use for STR testing?
Flags: needinfo?(jmitchell)
Comment 20•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #19) > (In reply to Joshua Mitchell [:Joshua_M] from comment #17) > > comment 15 addressed the steps-wanted request > > Josh - Do we know if comment 15 can be consistently reproducible to use for > STR testing? Apparently not - 15 minutes of "moving briskly about the 'Improve Firefox OS' settings, taking screenshots" did not repro this crash (in that reported build) Re-adding Steps-wanted
Flags: needinfo?(jmitchell)
Keywords: steps-wanted
Comment 21•10 years ago
|
||
cleaning keywords - please re-tag if this issue is seen again
Keywords: steps-wanted
Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Mass resolving WFM: signature(s) hasn't(/haven't) reported in past 28 days.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•