Closed
Bug 1058780
Opened 10 years ago
Closed 10 years ago
sync_merge() failures in automation runs.
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: bhargavg1, Assigned: sotaro)
References
Details
(Whiteboard: [CR 712258])
We are seeing sync_merge() failures in automation runs:
877 E Fence : merge: sync_merge("FramebufferSurface:0", 107, 190) returned an error: Not a typewriter (-25)
08-21 15:40:08.014 232 877 E Fence : merge: sync_merge("FramebufferSurface:1", 101, 212) returned an error: Bad file number (-9)
08-21 15:40:34.284 232 877 E Surface : dequeueBuffer: error duping fence: 9
Hence, creation of acquire fence fd fails so bogus fd is sent to GPU. GPU keeps on working on bogus fd or becomes unresponsive. Consequentially, display driver reports sync fence timeout on the acquire fence of FB layer (since it never signals).
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.0?
Flags: needinfo?(sotaro.ikeda.g)
Assignee | ||
Comment 2•10 years ago
|
||
This bug seems similar to Bug 1057220.
Flags: needinfo?(sotaro.ikeda.g)
Assignee | ||
Updated•10 years ago
|
Comment 3•10 years ago
|
||
(Perhaps preemptively) marking as a dupe of bug 1057220 where there will be patches.
Status: NEW → RESOLVED
blocking-b2g: 2.0? → 2.0+
Closed: 10 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 4•10 years ago
|
||
bug 1057220 will not have patches to fix. The bug is for finding actual bugs by logging and testing. Current actual open bugs are bug 1058366 and bug 1058368.
Comment 5•10 years ago
|
||
Thanks, Sotaro. Unduping (and sorry).
Sotaro, can you take this?
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 6•10 years ago
|
||
Ok, I take this bug. Currently we need to wait bug 1058366 and bug 1058368 fix.
Assignee | ||
Updated•10 years ago
|
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Comment 7•10 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #6)
> Currently we need to wait bug 1058366 and bug 1058368 fix.
Actually Bug 1054929 and Bug 1058366.
(In reply to Sotaro Ikeda [:sotaro] from comment #7)
> (In reply to Sotaro Ikeda [:sotaro] from comment #6)
> > Currently we need to wait bug 1058366 and bug 1058368 fix.
>
> Actually Bug 1054929 and Bug 1058366.
Infact just the Bug 1054929, for Bug 1058366 its POVB and change is being landed.
Comment 9•10 years ago
|
||
This seems to be fixed, haven't seen since AU 60.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v2.0:
--- → fixed
status-b2g-v2.1:
--- → fixed
status-b2g-v2.2:
--- → unaffected
status-firefox32:
--- → wontfix
status-firefox33:
--- → wontfix
status-firefox34:
--- → fixed
Target Milestone: --- → mozilla34
You need to log in
before you can comment on or make changes to this bug.
Description
•