Closed
Bug 1851636
Opened 1 year ago
Closed 1 year ago
Crash in [@ mozilla::layers::CanvasEventRingBuffer::SetNewBuffer]
Categories
(Core :: Graphics: Canvas2D, defect)
Core
Graphics: Canvas2D
Tracking
()
RESOLVED
FIXED
119 Branch
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox117 | --- | unaffected |
firefox118 | --- | unaffected |
firefox119 | + | fixed |
People
(Reporter: aryx, Assigned: bobowen)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(1 file)
4 GPU crashes from 4 installations of Firefox 119.0a1.
Crash report: https://crash-stats.mozilla.org/report/index/af595d96-0d3b-4bb3-878b-25f220230904
MOZ_CRASH Reason: MOZ_RELEASE_ASSERT(!mSharedMemory) (Shared memory should have been dropped before new buffer is sent.)
Top 10 frames of crashing thread:
0 xul.dll mozilla::layers::CanvasEventRingBuffer::SetNewBuffer gfx/layers/CanvasDrawEventRecorder.cpp:128
1 xul.dll mozilla::layers::CanvasTranslator::RecvNewBuffer::<lambda_11>::operator gfx/layers/ipc/CanvasTranslator.cpp:164
1 xul.dll mozilla::detail::RunnableFunction<`lambda at /builds/worker/checkouts/gecko/gfx/layers/ipc/CanvasTranslator.cpp:164:3'>::Run xpcom/threads/nsThreadUtils.h:548
2 xul.dll mozilla::TaskQueue::Runner::Run xpcom/threads/TaskQueue.cpp:257
3 xul.dll nsThreadPool::Run xpcom/threads/nsThreadPool.cpp:343
4 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1193
5 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:480
5 xul.dll mozilla::ipc::MessagePumpForNonMainThreads::Run ipc/glue/MessagePump.cpp:300
6 xul.dll MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:370
6 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:363
Flags: needinfo?(bobowencode)
Updated•1 year ago
|
tracking-firefox119:
--- → +
Assignee | ||
Comment 1•1 year ago
|
||
Hmm, my first suspicion here is the reader has failed for some reason, so never gets to the drop buffer.
If it is the case, I ought to be able to detect (and should have been detecting :-) ) that and not create and send the new buffer.
Assignee: nobody → bobowencode
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•1 year ago
|
||
Flags: needinfo?(bobowencode)
Assignee | ||
Comment 3•1 year ago
|
||
Pushed by bobowencode@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/f1db1cd01b38
Don't create a new buffer if we fail to process the drop buffer event. r=jrmuizel
Comment 5•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 119 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•