Open Bug 1951432 Opened 1 year ago Updated 1 year ago

Crash in [@ std::reverse] via TryEnumerableOwnPropertiesNative on Intel Raptor Lake CPUs

Categories

(Core :: JavaScript Engine, defect, P5)

Other
Windows
defect

Tracking

()

Tracking Status
firefox138 --- affected

People

(Reporter: release-mgmt-account-bot, Unassigned)

References

(Blocks 4 open bugs)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/6ed31fb3-a785-49a5-88e4-b51c40240907

Reason: EXCEPTION_ACCESS_VIOLATION_WRITE

Top 5 frames of crashing thread:

0  xul.dll  std::reverse  /builds/worker/fetches/vs/VC/Tools/MSVC/14.39.33519/include/xutility:6172
0  xul.dll  TryEnumerableOwnPropertiesNative  js/src/builtin/Object.cpp:1818
0  xul.dll  js::obj_keys  js/src/builtin/Object.cpp:2134
0  xul.dll  js::jit::ObjectKeys  js/src/jit/VMFunctions.cpp:1470
1  ?  @0x000002c5d78b643e  

By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:

  • First crash report: 2024-12-24
  • Process type: Content
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: Yes - 2 out of 7 crashes happened on null or near null memory address

The Bugbug bot thinks this bug should belong to the 'Core::JavaScript Engine: JIT' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: General → JavaScript Engine: JIT

Most common adapter device ID is "Raptor Lake-S UHD Graphics (0xa788)" so I suspect this is bad hardware.

Component: JavaScript Engine: JIT → JavaScript Engine
Summary: Crash in [@ std::reverse] → Crash in [@ std::reverse] via TryEnumerableOwnPropertiesNative

Yes, all crashes are from CPUs with CPU info family 6 model 183 stepping 1, this is our good friend Raptor Lake.

Blocks: cpu-bugs
Summary: Crash in [@ std::reverse] via TryEnumerableOwnPropertiesNative → Crash in [@ std::reverse] via TryEnumerableOwnPropertiesNative on Intel Raptor Lake CPUs
Severity: -- → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.