Closed
Bug 1749278
Opened 3 years ago
Closed 3 years ago
Crash in [@ mozilla::widget::WinWindowOcclusionTracker::UpdateOcclusionState]
Categories
(Core :: Widget: Win32, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1741452
People
(Reporter: gsvelto, Unassigned)
Details
(Keywords: crash, csectype-uaf, sec-high)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/84b2dce3-0384-4ca3-8b1f-9745d0220110
Reason: EXCEPTION_ACCESS_VIOLATION_READ
Top 10 frames of crashing thread:
0 xul.dll mozilla::widget::WinWindowOcclusionTracker::UpdateOcclusionState widget/windows/WinWindowOcclusionTracker.cpp:626
1 xul.dll mozilla::detail::RunnableFunction<`lambda at /builds/worker/checkouts/gecko/widget/windows/WinWindowOcclusionTracker.cpp:968:35'>::Run xpcom/threads/nsThreadUtils.h:531
2 xul.dll mozilla::widget::SerializedTaskDispatcher::HandleTasks widget/windows/WinWindowOcclusionTracker.cpp:263
3 xul.dll mozilla::detail::runnable_args_base<mozilla::detail::NoResult>::Run dom/media/webrtc/transport/runnable_utils.h:41
4 xul.dll mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:771
5 xul.dll mozilla::TaskController::ProcessPendingMTTask xpcom/threads/TaskController.cpp:391
6 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1195
7 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:107
8 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:324
9 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:306
At least one of these crashes appears to be stack corruption, but IIUC this code is pref'd off so these crashes must be coming from users who are deliberately enabling this code.
Comment 1•3 years ago
|
||
Is this a dupe of bug 1741452? Thanks.
Comment 2•3 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #1)
Is this a dupe of bug 1741452? Thanks.
Yes, it is dupe of bug 1741452.
Flags: needinfo?(sotaro.ikeda.g)
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Updated•1 year ago
|
Group: dom-core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•