Closed Bug 1355973 Opened 7 years ago Closed 2 years ago

The displayed crashing thread is not the always the same that one got with ProcessedCrash

Categories

(Socorro :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: calixte, Unassigned)

Details

The crashing thread displayed at https://crash-stats.mozilla.com/report/index/4adee317-f08a-4a83-8e73-2d1c12170412 shows:

0 	ntdll.dll	NtWaitForSingleObject	
1 	ntdll.dll	RtlpWaitOnCriticalSection	
2 	ntdll.dll	RtlpAllocateListLookup	
3 	mozglue.dll	malloc_impl	memory/build/replace_malloc.c:151
4 	xul.dll	mozilla::Vector<js::jit::MBasicBlock*, 1, js::SystemAllocPolicy>::convertToHeapStorage(unsigned int)	obj-firefox/dist/include/mozilla/Vector.h:936
5 	xul.dll	mozilla::Vector<js::jit::MBasicBlock*, 4, js::SystemAllocPolicy>::growStorageBy(unsigned int)	obj-firefox/dist/include/mozilla/Vector.h:1027
6 	xul.dll	js::jit::MIRGraph::removeSuccessorBlocks(js::jit::MBasicBlock*)	js/src/jit/MIRGraph.cpp:194
7 	xul.dll	js::jit::IonBuilder::restartLoop(js::jit::CFGBlock const*)	js/src/jit/IonBuilder.cpp:2355 

and in the json got from https://crash-stats.mozilla.com/api/ProcessedCrash/?crash_id=4adee317-f08a-4a83-8e73-2d1c12170412&datatype=processed:

mozilla::`anonymous namespace'::RunWatchdog
_PR_NativeRunThread
pr_root
_o__CIpow
BaseThreadInitThunk
__RtlUserThreadStart
_RtlUserThreadStart
Which one is the correct one?
According to the signature, I'd say that the displayed one is correct, but I'm not sure.

All this data has aged out and there isn't enough data codified in this bug to guess at what it looked like, so I'm going to close it out. I haven't heard anyone mention this, so I'm going to mark it WORKSFORME.

If this is still happening, please reopen with specifics.

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.