DNS Service missed its message so mozilla hung

RESOLVED INCOMPLETE

Status

()

Core
Networking
--
critical
RESOLVED INCOMPLETE
15 years ago
2 years ago

People

(Reporter: timeless, Unassigned)

Tracking

({hang})

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
note: this was the end of me running mozilla, semi seriously using it, unlike
the other bugs i've filed in network recently which were mostly xpcshell.

Main thread #8:
NTDLL! 77f8a122()
KERNEL32! 77e88787()
_PR_WaitCondVar(PRThread * 0x00282800, PRCondVar * 0x015148d8, PRLock *
0x00282a80, unsigned int 4294967295) line 201 + 23 bytes
PR_WaitCondVar(PRCondVar * 0x015148d8, unsigned int 4294967295) line 548 + 23 bytes
PR_JoinThread(PRThread * 0x0104e480) line 1577 + 11 bytes
nsThread::Join(nsThread * const 0x0104e380) line 185 + 13 bytes
nsDNSService::ShutdownInternal() line 1867 + 26 bytes
nsDNSService::Observe(nsDNSService * const 0x0104e140, nsISupports * 0x0027d764,
const char * 0x10111240, const unsigned short * 0x00000000) line 1310
nsObserverService::NotifyObservers(nsObserverService * const 0x00fc4d10,
nsISupports * 0x0027d764, const char * 0x10111240, const unsigned short *
0x00000000) line 213
NS_ShutdownXPCOM(nsIServiceManager * 0x00000000) line 694
main(int 3, char * * 0x00284790) line 1911 + 8 bytes
mainCRTStartup() line 338 + 17 bytes
KERNEL32! 77e87903()

DNS (Victim) thread #1:
USER32! 77e1414f()
nsDNSService::Run(nsDNSService * const 0x0104e13c) line 1453 + 21 bytes
nsThread::Main(void * 0x0104e380) line 123 + 26 bytes
_PR_NativeRunThread(void * 0x0104e480) line 433 + 13 bytes
MSVCRTD! 1020c323()
KERNEL32! 77e92ca8()

Timer thread #2:
NTDLL! 77f8a122()
KERNEL32! 77e88787()
_PR_WaitCondVar(PRThread * 0x0151d2a0, PRCondVar * 0x01082ae0, PRLock *
0x0107a240, unsigned int 4294967295) line 201 + 23 bytes
PR_WaitCondVar(PRCondVar * 0x01082ae0, unsigned int 4294967295) line 548 + 23 bytes
TimerThread::Run(TimerThread * const 0x01051a10) line 262 + 17 bytes
nsThread::Main(void * 0x010619f0) line 123 + 26 bytes
_PR_NativeRunThread(void * 0x0151d2a0) line 433 + 13 bytes
MSVCRTD! 1020c323()
KERNEL32! 77e92ca8()

Unknown Thread A #3:
NTDLL! 77f87e77()
USER32! 77e1464c()
USER32! 77e14718()
SHLWAPI! 77c71991()
SHLWAPI! 77c75e56()
SHLWAPI! 77c75dbc()

Unknown Thread B #4:
NTDLL! 77f82eec()
RPCRT4! 77d4b407()
RPCRT4! 77d4b771()
KERNEL32! 77e92ca8()

Unknown Thread C #5:
NTDLL! 77f87e77()
KERNEL32! 77e9e68a()
KERNEL32! 77e92ca8()

Memory Flusher Thread #6:
NTDLL! 77f8a122()
KERNEL32! 77e88787()
_PR_WaitCondVar(PRThread * 0x002776e8, PRCondVar * 0x00277530, PRLock *
0x00277478, unsigned int 4474380) line 201 + 23 bytes
PR_WaitCondVar(PRCondVar * 0x00277530, unsigned int 4474380) line 548 + 23 bytes
MemoryFlusher::Run(MemoryFlusher * const 0x00277420) line 168 + 20 bytes
nsThread::Main(void * 0x002775e8) line 123 + 26 bytes
_PR_NativeRunThread(void * 0x002776e8) line 433 + 13 bytes
MSVCRTD! 1020c323()
KERNEL32! 77e92ca8()

Unknown Thread D #7:
NTDLL! 77f8a122()
KERNEL32! 77e88787()
8b000000()

Unknown Thread E #9:
NTDLL! 77f82eec()
RPCRT4! 77d4b407()
RPCRT4! 77d4b771()
KERNEL32! 77e92ca8()

While i have triggered other interesting things during the course of this
session (including one potential xpconnect/xpcom deadlock), the only thing i did
recently was temporarily break and change assertions from nop to int 3. i can't
imagine that it'd cause windows/mozilla to lose the dns close message, i'll have
to check to see if messages are gauranteed to be delivered.

Comment 1

15 years ago
-> gordon (enjoy!)
Assignee: new-network-bugs → gordon

Comment 2

15 years ago
I hit this as well in the debugger, other than heavy memory usage from a large
page, nothing unusual was done by me.

Updated

9 years ago
Assignee: gordon → nobody
Severity: normal → critical
QA Contact: benc → networking

Comment 3

7 years ago
timeless, David, still seeing this?

a couple DNS hang issues were fixed a while ago in bug 467562  and bug 470274.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.