Closed
Bug 1686773
Opened 5 years ago
Closed 5 years ago
Crash in [@ mozilla::gfx::VsyncBridgeChild::Close]
Categories
(Core :: Graphics, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: worcester12345, Unassigned)
Details
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/405b26d4-ec20-4327-94b0-45fa10210114
Reason: EXCEPTION_ACCESS_VIOLATION_READ
Top 10 frames of crashing thread:
0 xul.dll mozilla::gfx::VsyncBridgeChild::Close gfx/ipc/VsyncBridgeChild.cpp:99
1 xul.dll mozilla::detail::RunnableMethodImpl< xpcom/threads/nsThreadUtils.h:1240
2 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1197
3 xul.dll mozilla::ipc::MessagePumpForNonMainThreads::Run ipc/glue/MessagePump.cpp:332
4 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:327
5 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:309
6 xul.dll static nsThread::ThreadFunc xpcom/threads/nsThread.cpp:442
7 nss3.dll _PR_NativeRunThread nsprpub/pr/src/threads/combined/pruthr.c:399
8 nss3.dll pr_root nsprpub/pr/src/md/windows/w95thred.c:139
9 ucrtbase.dll thread_start<unsigned int , 1>
|
||
Updated•5 years ago
|
Component: General → Graphics
Product: Firefox → Core
|
||
Updated•5 years ago
|
Severity: -- → S4
Priority: -- → P3
|
||
Comment 1•5 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
|
Reporter | |
Comment 2•5 years ago
|
||
(In reply to Release mgmt bot [:sylvestre / :calixte / :marco for bugbug] from comment #1)
Closing because no crashes reported for 12 weeks.
Is this process standard across all components of Mozilla/Bugzilla?
Is this new? First I am seeing it, and I'm sure there are many other bugs out there which need this applied. This just spurs on new/duplicate bugs. I don't see the reason to not just leave it open. You should mark them "WONTFIX" instead.
You need to log in
before you can comment on or make changes to this bug.
Description
•