Open Bug 1982261 Opened 8 days ago Updated 7 days ago

Crash in [@ IPCError-browser | SetCookies Invalid cookie received.]

Categories

(Core :: DOM: Core & HTML, defect)

Other
All
defect

Tracking

()

Tracking Status
firefox-esr128 --- unaffected
firefox-esr140 --- unaffected
firefox141 --- unaffected
firefox142 --- fix-optional
firefox143 --- affected

People

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

References

(Blocks 1 open bug, Regression)

Details

(Keywords: crash, regression)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/ee441322-b777-4419-8e5d-bffec0250723

Reason: DUMP_REQUESTED

Top 10 frames of crashing thread:

0  libxul.so  mozilla::dom::binding_detail::GenericGetter<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ThrowExceptions>  dom/bindings/BindingUtils.cpp
0  libxul.so  CallJSNative  js/src/vm/Interpreter.cpp:501
0  libxul.so  js::InternalCallOrConstruct  js/src/vm/Interpreter.cpp:597
0  libxul.so  InternalCall  js/src/vm/Interpreter.cpp:664
0  libxul.so  js::Call  js/src/vm/Interpreter.cpp:696
0  libxul.so  js::CallGetter  js/src/vm/Interpreter.cpp:818
0  libxul.so  CallGetter  js/src/vm/NativeObject.cpp:2125
0  libxul.so  GetExistingProperty<  js/src/vm/NativeObject.cpp:2153
0  libxul.so  NativeGetPropertyInline<  js/src/vm/NativeObject.cpp:2296
0  libxul.so  js::NativeGetProperty  js/src/vm/NativeObject.cpp:2326

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

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

By analyzing the backtrace, the regression may have been introduced by a patch [1] to fix Bug 1976971.

[1] https://hg.mozilla.org/mozilla-central/rev?node=9638f25e3a87

:jrmuizel, since you are the author of the potential regressor, could you please take a look?

Flags: needinfo?(jmuizelaar)

Set release status flags based on info from the regressing bug 1976971

You need to log in before you can comment on or make changes to this bug.