Closed
Bug 949169
Opened 11 years ago
Closed 10 years ago
[Monkey Test] IPC Crash on jb_gonk
Categories
(Core :: IPC, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: tkundu, Unassigned)
Details
(Keywords: crash, regression, Whiteboard: [CR 588094][b2g-crash][osrestartcrash])
Crash Data
Attachments
(2 files)
We are seeing IPC crash on FFOS 1.3 during monkey testing. I attached ".extra" file for it.
Reporter | ||
Comment 1•11 years ago
|
||
stack trace
Updated•11 years ago
|
Component: General → Graphics: Layers
Product: Firefox OS → Core
Comment 2•11 years ago
|
||
Changed the component depends on attachment 8346155 [details].
Updated•11 years ago
|
blocking-b2g: --- → 1.3?
Whiteboard: [CR 588094]
Reporter | ||
Comment 3•11 years ago
|
||
gaia/gecko revisions where we saw it: "gaia" last commit SHA1="1abda08e450cb66a61a31bdcfd3352e2df9d9ace" "gecko" last commit SHA1="e5638ae70aad34961a65e6a51b15ffe2f3553b0d"
Comment 4•11 years ago
|
||
Sotaro, Can you please take a look here or reassign appropriately?
Flags: needinfo?(sotaro.ikeda.g)
Comment 5•11 years ago
|
||
Test Steps: 1. Copied different format video to the phone. 2. Opened video application. 3. Played a video. 4. OS rebooted.
Comment 6•11 years ago
|
||
Greg, how often the crash happen? Which video are you using for test? H.264? WebM?
Flags: needinfo?(sotaro.ikeda.g) → needinfo?(ggrisco)
Comment 7•11 years ago
|
||
Grag, do you know the video format when the crash happens.
Comment 8•11 years ago
|
||
We've only seen this happen only once so far. Not sure what video format it is, except that it's not webm because software decoder is not being used.
Flags: needinfo?(ggrisco)
Comment 9•11 years ago
|
||
We've only seen this happen only once so far. Not sure what video format it is, except that it's not webm because software decoder is not being used.
Comment 10•11 years ago
|
||
From attachment 8346155 [details], crash happened at shmem allocation. But hw codec uses only uses gralloc. So, from Comment 9, crash seems not directly related to video buffer. ---------------------------------------------- 2 libxul.so!mozilla::ipc::Shmem::OpenExisting(mozilla::ipc::Shmem::IHadBetterBeIPDLCodeCallingThis_OtherwiseIAmADoodyhead, IPC::Message const&, int*, bool) [Shmem.cpp : 564 + 0x15] 3 libxul.so!mozilla::layers::PCompositorParent::OnMessageReceived(IPC::Message const&) [PCompositorParent.cpp : 375 + 0x9
Updated•10 years ago
|
Keywords: crash,
regression
Whiteboard: [CR 588094] → [CR 588094][b2g-crash][osrestartcrash]
Updated•10 years ago
|
blocking-b2g: 1.3? → 1.3+
Comment 11•10 years ago
|
||
What's a good way to reproduce this? Or do we just have the stack+code inspection to go on? Nicolas, anything obvious from the stack?
Flags: needinfo?(nical.bugzilla)
Comment 12•10 years ago
|
||
(In reply to Milan Sreckovic [:milan] from comment #11) > Nicolas, anything obvious from the stack? I don't remember ever running into this assertion. As Sotaro points out, this is a shmem thing so it's very unlikely that it was caused by hardware-accelerated video decoding/compositing (H264 videos) which use gralloc. Throwing wild uneducated guesses: * could we have run out of memory and failed to allocate a shmem because of that? * could we be asking for a huge shmem size (because of some unitialized variable, int overflow or whatnot)? googling the error shows that this assertion has been hit in the past: https://bugzilla.mozilla.org/show_bug.cgi?id=599059 https://bugzilla.mozilla.org/show_bug.cgi?id=548437
Flags: needinfo?(nical.bugzilla)
Updated•10 years ago
|
Component: Graphics: Layers → IPC
Comment 13•10 years ago
|
||
Ben Turner and I just took a look at this. It looks like it might just be an OOM situation. If it's only happened once in monkey testing, does it need to remain a certification blocker?
Comment 14•10 years ago
|
||
Looking at our database we haven't seen the crash reproduce this year yet, so lets not spend more time here until it does
Status: NEW → RESOLVED
blocking-b2g: 1.3+ → ---
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•