Open Bug 1495374 Opened 6 years ago Updated 2 years ago

Crash in js::frontend::ParseNodeAllocator::allocNode

Categories

(Core :: JavaScript Engine, defect, P5)

x86_64
Windows 10
defect

Tracking

()

Tracking Status
firefox64 --- affected

People

(Reporter: baffclan, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-aacaba35-3891-4c15-95f7-0b04c0181001. ============================================================= Top 10 frames of crashing thread: 0 xul.dll js::frontend::ParseNodeAllocator::allocNode js/src/frontend/ParseNode.cpp:55 1 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::primaryExpr js/src/frontend/Parser.cpp:11049 2 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::memberExpr js/src/frontend/Parser.cpp:9592 3 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::unaryExpr js/src/frontend/Parser.cpp:9388 4 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::unaryExpr js/src/frontend/Parser.cpp:9298 5 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::orExpr js/src/frontend/Parser.cpp:8836 6 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::condExpr js/src/frontend/Parser.cpp:8912 7 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::assignExpr js/src/frontend/Parser.cpp:9058 8 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::expr js/src/frontend/Parser.cpp:8689 9 xul.dll js::frontend::GeneralParser<js::frontend::FullParseHandler, char16_t>::condition js/src/frontend/Parser.cpp:4700 ============================================================= Application Basics: Name: Firefox Version: 64.0a1 Build ID: 20180930220130 Update Channel: nightly User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 OS: Windows_NT 10.0

One machine, x86, all crashes happened within 1 minute and we never saw it again. This could be disk corruption of the executable, memory corruption, etc.

Status: NEW → UNCONFIRMED
Ever confirmed: false
Priority: -- → P5
QA Whiteboard: qa-not-actionable

The bug has a crash signature, thus the bug will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: critical → S3
You need to log in before you can comment on or make changes to this bug.