Closed
Bug 1307761
Opened 8 years ago
Closed 7 years ago
Intermittent leakcheck | default process: 344 bytes leaked (CancelableRunnable, CondVar, Mutex, Runnable, nsTimer, ...)
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: intermittent-bug-filer, Unassigned)
References
Details
(Keywords: bulk-close-intermittents, intermittent-failure, memory-leak)
Filed by: tomcat [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=37070000&repo=mozilla-inbound https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-inbound-win32-debug/1475651521/mozilla-inbound_win7_vm-debug_test-mochitest-e10s-devtools-chrome-6-bm129-tests1-windows-build668.txt.gz
Comment 1•8 years ago
|
||
The log contains: [Parent 2607] ###!!! ASSERTION: Non-empty event queue being destroyed; events being leaked.: 'IsEmpty()', file /builds/slave/fx-team-lx-d-00000000000000000/build/src/xpcom/threads/nsEventQueue.cpp, line 36 #01: nsEventQueue::~nsEventQueue [xpcom/threads/nsEventQueue.cpp:35] #02: nsThread::~nsThread [mfbt/RefPtr.h:77] #03: nsThread::~nsThread [memory/mozalloc/mozalloc.h:218] #04: nsThread::Release [xpcom/threads/nsThread.cpp:174] #05: mozilla::RefPtrTraits<nsThread>::Release [mfbt/RefPtr.h:40] I don't know how to tell what the event actually is.
Comment 2•8 years ago
|
||
From bug 1204784 comment 39 it looks like one possible way to investigate is to use the XPCOM_MEM_LOG_CLASSES stuff, though given that this leak only seems to happen once a week that could be tough to reproduce.
Component: General → XPCOM
Status: NEW → RESOLVED
Closed: 7 years ago
Keywords: bulk-close-intermittents
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•