Closed
Bug 1664313
Opened 4 years ago
Closed 2 years ago
Crash in [@ IPCError-browser | ShutDownKill | PR_MD_WAIT_CV | PR_Wait | nsThread::Init]
Categories
(Core :: XPCOM, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox83 | --- | affected |
People
(Reporter: sefeng, Unassigned)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/7a3c8ef4-2cf4-469c-a363-efa0e0200908
Top 10 frames of crashing thread:
0 ntdll.dll NtWaitForSingleObject
1 kernelbase.dll WaitForSingleObjectEx
2 nss3.dll PR_MD_WAIT_CV nsprpub/pr/src/md/windows/w95cv.c:252
3 nss3.dll PR_Wait nsprpub/pr/src/threads/prmon.c:305
4 xul.dll nsThread::Init xpcom/threads/nsThread.cpp:676
5 xul.dll nsThreadManager::NewNamedThread xpcom/threads/nsThreadManager.cpp:628
6 xul.dll NS_NewNamedThread xpcom/threads/nsThreadUtils.cpp:161
7 xul.dll nsThreadPool::PutEvent xpcom/threads/nsThreadPool.cpp:115
8 xul.dll nsThreadPool::Dispatch xpcom/threads/nsThreadPool.cpp:350
9 xul.dll mozilla::net::nsStreamTransportService::Dispatch netwerk/base/nsStreamTransportService.cpp:288
I read the stack trace as the thread has received the shutdown signature, then it starts to create a memory report which requires to start a new thread, and it's blocked by https://hg.mozilla.org/mozilla-central/annotate/d4e11195e39888686d843a146a893eb0ebf38224/xpcom/threads/nsThread.cpp#l676
So I guess this could be a potential deadlock issue?
Reporter | ||
Updated•4 years ago
|
Crash Signature: [@ IPCError-browser | ShutDownKill | PR_MD_WAIT_CV | PR_Wait | nsThread::Init] → [@ IPCError-browser | ShutDownKill | PR_MD_WAIT_CV | PR_Wait | nsThread::Init]
[@ IPCError-browser | ShutDownKill | _PR_MD_WAIT_CV | PR_Wait | nsThread::Init ]
Updated•4 years ago
|
status-firefox83:
--- → affected
Comment 1•2 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•