Closed
Bug 1164513
Opened 9 years ago
Closed 9 years ago
Crash in GetGraphicBuffer while stability testing
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: ggrisco, Assigned: sotaro)
References
Details
(Keywords: crash, Whiteboard: [b2g-crash][caf-crash 505][caf priority: p1][CR 837243])
Crash Data
Attachments
(5 files, 1 obsolete file)
141.70 KB,
text/plain
|
Details | |
484.59 KB,
text/plain
|
Details | |
140.86 KB,
text/plain
|
Details | |
498.58 KB,
text/plain
|
Details | |
2.03 KB,
patch
|
sotaro
:
review+
jocheng
:
approval-mozilla-b2g37+
|
Details | Diff | Splinter Review |
Saw this crash signature a couple of times on latest build:
[@ mozilla::OffTheBooksMutex::Lock | mozilla::layers::SharedBufferManagerParent::GetGraphicBuffer | mozilla::layers::SharedBufferManagerParent::GetGraphicBuffer | mozilla::layers::GetGraphicBufferFrom ]
In both instances of this crash, seeing this at the end of the log:
05-12 21:24:54.614 268 2812 E HWComposer: Non-uniform vsync interval: 650007031
cafbot will upload minidump and extra file (with logs).
Comment 1•9 years ago
|
||
Comment 2•9 years ago
|
||
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to Greg Grisco from comment #0)
> In both instances of this crash, seeing this at the end of the log:
>
> 05-12 21:24:54.614 268 2812 E HWComposer: Non-uniform vsync interval:
> 650007031
>
> cafbot will upload minidump and extra file (with logs).
The following log exits before the above log. It seems to related to the problem.
> [Parent 264] WARNING: pipe error (279): Connection reset by peer:
Assignee | ||
Comment 4•9 years ago
|
||
Implementation of SharedBufferManagerParent::GetGraphicBuffer() seems to have a problem.
It does not handle a case that SharedBufferManagerParent of mOwner is already destroyed.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Comment 5•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Attachment #8605408 -
Flags: review?(nical.bugzilla)
Assignee | ||
Comment 6•9 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #3)
>
> The following log exits before the above log. It seems to related to the
> problem.
>
> > [Parent 264] WARNING: pipe error (279): Connection reset by peer:
It means, parent side detect IPC connection problem and the connection is disconnected. It typically happens when child process freeze or crash.
Updated•9 years ago
|
Whiteboard: [CR 837243] → [caf priority: p1][CR 837243]
Updated•9 years ago
|
Whiteboard: [caf priority: p1][CR 837243] → [b2g-crash][caf-crash 505][caf priority: p1][CR 837243]
Comment 7•9 years ago
|
||
Observed on:
Device: msm8909
Gonk Version: AU_LINUX_GECKO_LF.BR.1.2.3.00.00.00.000.154
Moz BuildID: 20150511002500
Manifest: https://www.codeaurora.org/cgit/quic/lf/b2g/manifest/tree/caf_AU_LINUX_GECKO_LF.BR.1.2.3.00.00.00.000.154.xml?h=release
B2G Version: v2.2
Gecko Version: 37.0
Gaia: http://git.mozilla.org/?p=releases/gaia.git;a=commit;h=528ef60e7cda09ad43478065f5d33bda398fbeb7
Gecko: http://git.mozilla.org/?p=releases/gecko.git;a=commit;h=f7e168e362809afa274c2ecb9d346aeda90aa519
Patches: bug 1057091, bug 1162663, bug 1157029, bug 1155797, bug 1133147, bug 1156063, bug 1152439, bug 1156503, bug 1159434
Comment 8•9 years ago
|
||
Comment 9•9 years ago
|
||
Assignee | ||
Comment 10•9 years ago
|
||
Assignee | ||
Comment 12•9 years ago
|
||
Comment on attachment 8605408 [details] [diff] [review]
patch - Add nullptr check
Milan, can you review the patch? It is easy fix. And nical is PTO until next Tuesday.
Attachment #8605408 -
Flags: review?(nical.bugzilla) → review?(milan)
Comment on attachment 8605408 [details] [diff] [review]
patch - Add nullptr check
Review of attachment 8605408 [details] [diff] [review]:
-----------------------------------------------------------------
::: gfx/layers/ipc/SharedBufferManagerParent.cpp
@@ +363,5 @@
> android::sp<android::GraphicBuffer>
> SharedBufferManagerParent::GetGraphicBuffer(GrallocBufferRef aRef)
> {
> MonitorAutoLock lock(*sManagerMonitor.get());
> + if (!GetInstance(aRef.mOwner)) {
This would certainly fix the crash in this code. I'm assuming calling GetInstance twice (when we succeed) is OK, and there are no performance implications. Are the callers ready for nullptr? Just to make sure we don't crash in the caller instead.
Attachment #8605408 -
Flags: review?(milan) → review+
Assignee | ||
Comment 14•9 years ago
|
||
> Are the callers ready for nullptr?
I re-checked the code, there is a one place that nullptr check is not exist. The code is used only by layer scope now.
Assignee | ||
Comment 15•9 years ago
|
||
Apply the comment. Carry "r=milan".
Attachment #8605408 -
Attachment is obsolete: true
Attachment #8605932 -
Flags: review+
Assignee | ||
Comment 16•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox41:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
Assignee | ||
Updated•9 years ago
|
status-b2g-v2.2:
--- → affected
Assignee | ||
Comment 18•9 years ago
|
||
Comment on attachment 8605932 [details] [diff] [review]
patch - Add nullptr check
NOTE: 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 #): Bug 959089
User impact if declined: system boot could happen in some cases.
Testing completed: locally tested.
Risk to taking this patch (and alternatives if risky): low.
String or UUID changes made by this patch: none.
Attachment #8605932 -
Flags: approval-mozilla-b2g37?
Reporter | ||
Comment 19•9 years ago
|
||
I applied the patch internally and it will be built into AU 157+, thanks.
Updated•9 years ago
|
status-b2g-master:
--- → fixed
Updated•9 years ago
|
Attachment #8605932 -
Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
Updated•9 years ago
|
status-firefox39:
--- → wontfix
status-firefox40:
--- → wontfix
Comment 20•9 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•