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

NEW
Unassigned

Status

Socorro
General
8 months ago
8 months ago

People

(Reporter: calixte, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 months ago
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
(Reporter)

Comment 1

8 months ago
Same issue with this report: https://crash-stats.mozilla.com/report/index/a11be167-cc7e-4aba-8faf-4bbaa2170411
Which one is the correct one?
(Reporter)

Comment 3

8 months ago
According to the signature, I'd say that the displayed one is correct, but I'm not sure.
You need to log in before you can comment on or make changes to this bug.