Open Bug 1996491 Opened 25 days ago Updated 25 days ago

Crash in [@ mozilla::dom::CSSStyleProperties_Binding::GetPropertyValue] on Raptor Lake

Categories

(Core :: DOM: Bindings (WebIDL), defect)

Other
Windows
defect

Tracking

()

Tracking Status
firefox146 --- affected

People

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

References

(Blocks 3 open bugs)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/95d880ae-126e-4842-9480-28ded0251023

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0  xul.dll  mozilla::dom::CSSStyleProperties_Binding::GetPropertyValue  dom/bindings/CSSStylePropertiesBinding.cpp:57
1  xul.dll  mozilla::dom::binding_detail::GenericGetter<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions>  dom/bindings/BindingUtils.cpp:3179
2  ?  @0x0000019c8b5aa7f0  
3  ?  @0x0000019c8b78958a  
4  ?  @0x0000019c8ab15937  
5  ?  @0x0000019c8b5a6cae  
6  ?  @0x0000019c8b595250  
7  ?  @0x0000019c8a82142b  
8  xul.dll  EnterJit  js/src/jit/Jit.cpp:107
8  xul.dll  js::jit::MaybeEnterJit  js/src/jit/Jit.cpp:255

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

  • First crash report: 2025-09-02
  • Process type: Content
  • Is startup crash: No
  • Has user comments: No
  • Is null crash: No

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

90% of these crashes are on family 6 model 183 stepping 1. The linked crash is family 6 model 186 stepping 2 but maybe that's a similar problem.

Severity: -- → S3
Component: JavaScript Engine: JIT → DOM: Bindings (WebIDL)
Summary: Crash in [@ mozilla::dom::CSSStyleProperties_Binding::GetPropertyValue] → Crash in [@ mozilla::dom::CSSStyleProperties_Binding::GetPropertyValue] on Raptor Lake
You need to log in before you can comment on or make changes to this bug.