Closed Bug 544863 Opened 14 years ago Closed 12 years ago

Seems random crash at tp4 (EXCEPTION_ACCESS_VIOLATION, 0x0)

Categories

(Core :: General, defect)

x86
Windows Vista
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: masayuki, Unassigned)

References

Details

(Keywords: crash, intermittent-failure)

> Operating system: Windows NT
>                   6.0.6000 
> CPU: x86
>      GenuineIntel family 6 model 15 stepping 2
>      2 CPUs
> 
> Crash reason:  EXCEPTION_ACCESS_VIOLATION
> Crash address: 0x0
> 
> Thread 0 (crashed)
>  0  0x0
>     eip = 0x00000000   esp = 0x0025f3f8   ebp = 0x0025f8c4   ebx = 0x2e646562
>     esi = 0x006c6c64   edi = 0x00000000   eax = 0x00000000   ecx = 0x00000000
>     edx = 0x006c6c64   efl = 0x00210246
>     Found by: given as instruction pointer in context
>  1  xul.dll!nsBaseAppShell::OnProcessNextEvent(nsIThreadInternal *,int,unsigned int) [nsBaseAppShell.cpp:b21188a34531 : 293 + 0x16]
>     eip = 0x6b9a4f62   esp = 0x0025f8cc   ebp = 0x00000000
>     Found by: previous frame's frame pointer
>  2  xul.dll!nsThread::ProcessNextEvent(int,int *) [nsThread.cpp:b21188a34531 : 508 + 0x27]
>     eip = 0x6b98ead0   esp = 0x0025f948   ebp = 0x0025f984
>     Found by: call frame info with scanning
>  3  xul.dll!NS_ProcessPendingEvents_P(nsIThread *,unsigned int) [nsThreadUtils.cpp:b21188a34531 : 200 + 0xb]
>     eip = 0x6b8d8217   esp = 0x0025f98c   ebp = 0x0025f9ac
>     Found by: previous frame's frame pointer
>  4  xul.dll!mozilla::ShutdownXPCOM(nsIServiceManager *) [nsXPComInit.cpp:b21188a34531 : 769 + 0xa]
>     eip = 0x6ba9c666   esp = 0x0025f9b4   ebp = 0x0025f9dc
>     Found by: previous frame's frame pointer
>  5  xul.dll!ScopedXPCOMStartup::~ScopedXPCOMStartup() [nsAppRunner.cpp:b21188a34531 : 1042 + 0x6]
>     eip = 0x6bacf5e1   esp = 0x0025f9e4   ebp = 0x0025f9f0
>     Found by: previous frame's frame pointer
>  6  xul.dll!XRE_main [nsAppRunner.cpp:b21188a34531 : 3521 + 0x11]
>     eip = 0x6ba458ac   esp = 0x0025f9f8   ebp = 0x0025fc8c
>     Found by: previous frame's frame pointer
>  7  firefox.exe!wmain [nsWindowsWMain.cpp:b21188a34531 : 120 + 0xeb]
>     eip = 0x00cf133b   esp = 0x0025fc94   ebp = 0x0025fcd8
>     Found by: previous frame's frame pointer
>  8  firefox.exe!__tmainCRTStartup [crtexe.c:b21188a34531 : 591 + 0x18]
>     eip = 0x00cf16d2   esp = 0x0025fce0   ebp = 0x0025fd18
>     Found by: previous frame's frame pointer
>  9  kernel32.dll + 0x43832
>     eip = 0x76bf3833   esp = 0x0025fd20   ebp = 0x0025fd24   ebx = 0x7ffdf000
>     Found by: call frame info
> 10  ntdll.dll + 0x3a9bc
>     eip = 0x7750a9bd   esp = 0x0025fd2c   ebp = 0x0025fd64
>     Found by: previous frame's frame pointer

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1265614393.1265615869.4797.gz
WINNT 6.0 mozilla-central talos tp4 [testfailed] Started 23:33, finished 23:58
Blocks: 438871
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: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.