Open Bug 1682854 Opened 3 years ago Updated 2 years ago

Crash in [@ JSStructuredCloneWriter::startWrite]

Categories

(Core :: JavaScript Engine, defect, P2)

Unspecified
All
defect

Tracking

()

Tracking Status
firefox-esr78 --- affected
firefox86 --- affected
firefox87 --- affected
firefox88 --- affected
firefox89 --- ?

People

(Reporter: sg, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

(Keywords: crash, Whiteboard: [not-a-fission-bug], qa-not-actionable)

Crash Data

Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/85a9a3fa-81bd-4628-b467-73e790201211

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 9 frames of crashing thread:

0 xul.dll JSStructuredCloneWriter::startWrite js/src/vm/StructuredClone.cpp:1760
1 xul.dll WriteStructuredClone js/src/vm/StructuredClone.cpp:684
2 xul.dll JSAutoStructuredCloneBuffer::write js/src/vm/StructuredClone.cpp:3446
3 xul.dll mozilla::dom::StructuredCloneHolderBase::Write dom/base/StructuredCloneHolder.cpp:265
4 xul.dll mozilla::dom::StructuredCloneHolder::Write dom/base/StructuredCloneHolder.cpp:352
5 xul.dll mozilla::dom::StructuredCloneHolder::Write dom/base/StructuredCloneHolder.cpp:345
6 xul.dll static mozilla::dom::StructuredCloneBlob::Constructor dom/base/StructuredCloneBlob.cpp:70
7 xul.dll mozilla::dom::StructuredCloneHolder_Binding::_constructor dom/bindings/StructuredCloneHolderBinding.cpp:230
8  @0x16fb85e065c 

Several of the reports in Nightly are from various extensions.

Steve, would you mind taking a look? Can we release-assert something here...?

Flags: needinfo?(sphink)
Severity: -- → S2
Priority: -- → P1
OS: Windows → All
Whiteboard: [not-a-fission-bug]

The volume of this bug sounds really low at the moment, and except for the weirdness of the spikes on Feb 12, Feb 26, Mar 12 and Mar 29, I would suggest to close this bug.

What do you think Steve? Should we keep this bug open with a lower priority/severity or attempt to fix it soon-ish?

Priority: P1 → P2
Whiteboard: [not-a-fission-bug] → [not-a-fission-bug], qa-not-actionable

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: S2 → S3
You need to log in before you can comment on or make changes to this bug.