Closed Bug 1300972 Opened 9 years ago Closed 5 years ago

Crash in mozilla::layers::CanvasClientSharedSurface::UpdateRenderer

Categories

(Core :: Graphics, defect)

Unspecified
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: kanru, Assigned: kip)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-d1489a13-5e98-4e32-8c2a-2d3f82160906. ============================================================= This is a low volume crash from a single installation. I suspect it's a regression introduced by bug 1284324. ni Kip in case it's VR related.
Flags: needinfo?(kgilbert)
(In reply to Kan-Ru Chen [:kanru] (UTC+8) from comment #0) > This bug was filed from the Socorro interface and is > report bp-d1489a13-5e98-4e32-8c2a-2d3f82160906. > ============================================================= > > This is a low volume crash from a single installation. I suspect it's a > regression introduced by bug 1284324. > > ni Kip in case it's VR related. Thanks :kanru, This would indeed affect only VR users. I have reproduced this while tracking down Bug 1296446, which may be related. I'll take this bug as well.
Assignee: nobody → kgilbert
Flags: needinfo?(kgilbert)
See Also: → 1296446
When running debug builds, I can see that the BlitFrameBuffer call in GLScreenBuffer::AssureBlitted() is failing. I have not yet confirmed if this only happens only on the first frame, but allowing execution to continue results in correct rendering in the HMD and in the mirrored texture. The callstack in this case matches the one in this report, but deeper below the UpdateRenderer function. This difference may be due to optimization in non-debug builds. Perhaps if I can fix the failure reproducible in the debug builds, this will correct the core cause of this crash.
See Also: → 1326376
(In reply to :kip (Kearwood Gilbert) from comment #2) > When running debug builds, I can see that the BlitFrameBuffer call in > GLScreenBuffer::AssureBlitted() is failing. I have not yet confirmed if > this only happens only on the first frame, but allowing execution to > continue results in correct rendering in the HMD and in the mirrored texture. > > The callstack in this case matches the one in this report, but deeper below > the UpdateRenderer function. This difference may be due to optimization in > non-debug builds. > > Perhaps if I can fix the failure reproducible in the debug builds, this will > correct the core cause of this crash. Kip, I was investigating this issue as well. Please take a look at Bug 1326376 comment 17, probably, it would bring some ideas.
See Also: → 1432411

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.