"ASSERTION: no socket thread event target" while running leak test

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
11 years ago
7 years ago

People

(Reporter: dbaron, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Windows Server 2003
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

The Windows leak test box just went orange with:

--WEBSHELL 0949D090 == 4
--WEBSHELL 08ADD5A0 == 3
###!!! ASSERTION: no socket thread event target: 'Error', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/netwerk/protocol/http/src/nsHttpTransaction.cpp, line 541
necko!nsHttpConnection::OnSocketReadable+0x00000000000000DA (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\protocol\http\src\nshttpconnection.cpp, line 664)
necko!nsHttpConnection::OnInputStreamReady+0x00000000000000A5 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\protocol\http\src\nshttpconnection.cpp, line 762)
necko!nsSocketInputStream::OnSocketReady+0x0000000000000104 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransport2.cpp, line 257)
necko!nsSocketTransport::OnSocketReady+0x00000000000000DE (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransport2.cpp, line 1522)
necko!nsSocketTransportService::DoPollIteration+0x0000000000000320 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransportservice2.cpp, line 674)
necko!nsSocketTransportService::OnProcessNextEvent+0x000000000000004D (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransportservice2.cpp, line 539)
xpcom_core!nsThread::ProcessNextEvent+0x0000000000000128 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\xpcom\threads\nsthread.cpp, line 500)
xpcom_core!NS_ProcessNextEvent_P+0x0000000000000053 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\obj-firefox\xpcom\build\nsthreadutils.cpp, line 230)
necko!nsSocketTransportService::Run+0x00000000000000F7 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransportservice2.cpp, line 581)
xpcom_core!nsThread::ProcessNextEvent+0x00000000000001FA (e:\builds\moz2_slave\mozilla-central-win32-debug\build\xpcom\threads\nsthread.cpp, line 511)
xpcom_core!NS_ProcessNextEvent_P+0x0000000000000053 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\obj-firefox\xpcom\build\nsthreadutils.cpp, line 230)
xpcom_core!nsThread::ThreadFunc+0x00000000000000CE (e:\builds\moz2_slave\mozilla-central-win32-debug\build\xpcom\threads\nsthread.cpp, line 254)
nspr4!_PR_NativeRunThread+0x00000000000000DB (e:\builds\moz2_slave\mozilla-central-win32-debug\build\nsprpub\pr\src\threads\combined\pruthr.c, line 436)
nspr4!pr_root+0x0000000000000019 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\nsprpub\pr\src\md\windows\w95thred.c, line 122)
MSVCR80D!beginthreadex+0x0000000000000221
MSVCR80D!beginthreadex+0x00000000000001C7
kernel32!GetModuleHandleA+0x00000000000000DF


This could be related to bug 469514, but I haven't seen this one before.


The log is:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1237556183.1237561105.6609.gz
WINNT 5.2 mozilla-central leak test build on 2009/03/20 06:36:23
Whiteboard: [orange]
Blocks: 438871
Here's another on mozilla-central Window
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1242339690.1242344071.16303.gz

###!!! ASSERTION: no socket thread event target: 'Error', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/netwerk/protocol/http/src/nsHttpTransaction.cpp, line 541
necko!nsHttpConnection::OnSocketReadable+0x00000000000000DA (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\protocol\http\src\nshttpconnection.cpp, line 664)
necko!nsHttpConnection::OnInputStreamReady+0x00000000000000A5 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\protocol\http\src\nshttpconnection.cpp, line 762)
necko!nsSocketInputStream::OnSocketReady+0x0000000000000104 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransport2.cpp, line 257)
necko!nsSocketTransport::OnSocketReady+0x00000000000000DE (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransport2.cpp, line 1522)
necko!nsSocketTransportService::DoPollIteration+0x0000000000000320 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransportservice2.cpp, line 674)
necko!nsSocketTransportService::OnProcessNextEvent+0x000000000000001B (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransportservice2.cpp, line 538)
xpcom_core!nsThread::ProcessNextEvent+0x0000000000000128 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\xpcom\threads\nsthread.cpp, line 500)
xpcom_core!NS_ProcessNextEvent_P+0x0000000000000053 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\obj-firefox\xpcom\build\nsthreadutils.cpp, line 230)
necko!nsSocketTransportService::Run+0x00000000000000F7 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\netwerk\base\src\nssockettransportservice2.cpp, line 581)
xpcom_core!nsThread::ProcessNextEvent+0x00000000000001FA (e:\builds\moz2_slave\mozilla-central-win32-debug\build\xpcom\threads\nsthread.cpp, line 511)
xpcom_core!NS_ProcessNextEvent_P+0x0000000000000053 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\obj-firefox\xpcom\build\nsthreadutils.cpp, line 230)
xpcom_core!nsThread::ThreadFunc+0x00000000000000CE (e:\builds\moz2_slave\mozilla-central-win32-debug\build\xpcom\threads\nsthread.cpp, line 254)
nspr4!_PR_NativeRunThread+0x00000000000000DB (e:\builds\moz2_slave\mozilla-central-win32-debug\build\nsprpub\pr\src\threads\combined\pruthr.c, line 426)
nspr4!pr_root+0x0000000000000019 (e:\builds\moz2_slave\mozilla-central-win32-debug\build\nsprpub\pr\src\md\windows\w95thred.c, line 122)
MSVCR80D!beginthreadex+0x0000000000000221
MSVCR80D!beginthreadex+0x00000000000001C7
kernel32!GetModuleHandleA+0x00000000000000DF
###!!! ABORT: imgCacheEntry release isn't thread-safe!: '_mOwningThread.GetThread() == PR_GetCurrentThread()', file e:\builds\moz2_slave\mozilla-central-win32-debug\build\modules\libpr0n\src\imgLoader.h, line 78
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.