Closed
Bug 1031866
Opened 10 years ago
Closed 9 years ago
Crash in mozilla::layers::StreamTextureHost::Lock()
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1030934
People
(Reporter: gal, Assigned: jgilbert)
References
Details
(Keywords: regression)
We reliably crash with Nightly on this url: http://mrdoob.com/lab/javascript/threejs/css3d/ Here is the stack: https://crash-stats.mozilla.com/report/index/9863822a-b657-4485-9a22-ce4d82140629
Reporter | ||
Updated•10 years ago
|
Keywords: regression,
regressionwindow-wanted
![]() |
||
Comment 1•10 years ago
|
||
Dupe Bug 1030934 ?
Comment 2•10 years ago
|
||
(In reply to Alice0775 White from comment #1) > Dupe Bug 1030934 ? Possibly, the patch currently attached to bug 1030934 does stop the crash. I still get: [54949] WARNING: failed to lock front buffer: file /Users/msreckovic/Repos/mozilla-central/gfx/layers/composite/ImageHost.cpp, line 86 which seems a bit disconcerting.
Assignee: nobody → jgilbert
See Also: → 1030934
Comment 3•10 years ago
|
||
By the way, if this gets resolved as a duplicate of bug 1030934, let me know as it also shows a problem with Skia canvas on OS X.
Comment 4•10 years ago
|
||
Jeff, is this gone now that bug 1030934 is fixed?
Flags: needinfo?(jgilbert)
Assignee | ||
Comment 5•10 years ago
|
||
I can't repro the crash now, but I never tried to repro it before. Does it work for you now, Andreas?
Flags: needinfo?(jgilbert) → needinfo?(gal)
Assignee | ||
Comment 6•10 years ago
|
||
Specifically, when I try the testcase, it works for me without crashing. (cool testcase, by the way)
Comment 7•9 years ago
|
||
I was able to confirm the crashes on the 2014-06-29 nightly and the lack of crashes on the 2014-07-02 nightly, so calling this a dupe of bug 1030934. That said, I see pretty ugly rendering issues with this testcase on current nightly. I'll file that as a new bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(gal)
Keywords: regressionwindow-wanted
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•