Open Bug 1742004 Opened 4 years ago Updated 1 year ago

Crash in [@ mozilla::ipc::PortLink::SendMessage | IPC_Message_Name=PBackgroundLSSnapshot::Reply_LoadKeys]

Categories

(Core :: Storage: localStorage & sessionStorage, defect)

Unspecified
Windows 10
defect

Tracking

()

People

(Reporter: mccr8, Unassigned)

References

Details

(Keywords: crash, Whiteboard: dom-lws-bugdash-triage)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/1e7a896d-5eef-43ac-b890-9b7660211117

MOZ_CRASH Reason: MOZ_CRASH(IPC message size is too large)

Top 10 frames of crashing thread:

0 xul.dll mozilla::ipc::PortLink::SendMessage ipc/glue/MessageLink.cpp:98
1 xul.dll mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:1987
2 xul.dll mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1855
3 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1142
4 xul.dll mozilla::ipc::MessagePumpForNonMainThreads::Run ipc/glue/MessagePump.cpp:330
5 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:324
6 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:306
7 xul.dll static nsThread::ThreadFunc xpcom/threads/nsThread.cpp:390
8 nss3.dll _PR_NativeRunThread nsprpub/pr/src/threads/combined/pruthr.c:399
9 nss3.dll pr_root nsprpub/pr/src/md/windows/w95thred.c:139

I assume this is somehow related to bug 1706036.

See Also: → 1706036

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

(In reply to Jens Stutte [:jstutte] from comment #1)

I assume this is somehow related to bug 1706036.

This bug seems to be about trying to send too big messages from parent to child.
After a quick look, Reply_LoadKeys can end up doing this only when mOrderedItems is too large. Maybe there's a place where it's not properly synchronized with mValues.

Whiteboard: dom-lws-bugdash-triage
You need to log in before you can comment on or make changes to this bug.