Closed
Bug 1617180
Opened 5 years ago
Closed 3 years ago
Crash in [@ js::InitDateTimeState]
Categories
(Core :: JavaScript Engine, defect, P5)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: pascalc, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-0546816a-2053-4d2d-89c2-e21500200221.
Top 10 frames of crashing thread:
0 xul.dll js::InitDateTimeState js/src/vm/DateTime.cpp:516
1 xul.dll NS_InitXPCOM xpcom/build/XPCOMInit.cpp:441
2 xul.dll XREMain::XRE_main toolkit/xre/nsAppRunner.cpp:4697
3 xul.dll XRE_main toolkit/xre/nsAppRunner.cpp:4752
4 xul.dll mozilla::BootstrapImpl::XRE_main toolkit/xre/Bootstrap.cpp:45
5 firefox.exe NS_internal_main browser/app/nsBrowserApp.cpp:331
6 firefox.exe wmain toolkit/xre/nsWindowsWMain.cpp:131
7 firefox.exe __scrt_common_main_seh f:/dd/vctools/crt/vcstartup/src/startup/exe_common.inl:288
8 kernel32.dll BaseThreadInitThunk
9 ntdll.dll __RtlUserThreadStart
Seeing this signature in small volume on 74 beta, this seems to be a startup crash
|
||
Updated•5 years ago
|
Component: General → JavaScript Engine
|
||
Comment 1•5 years ago
|
||
Nicolas and I looked at this.
It appears to be some kind of hardware issue, or else heap corruption. Very low volume, quasirandom memory addresses. The code appears to be correct.
Priority: -- → P5
|
||
Comment 2•5 years ago
|
||
One thing to note, is that the crash address, even the lowest one with read/write violations seems to be dependent on the build-id.
|
|
||
Updated•4 years ago
|
Blocks: sm-defects-crashes
|
||
Comment 3•3 years ago
|
||
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•