Closed Bug 1624173 Opened 4 years ago Closed 2 years ago

Crash in [@ mozilla::ipc::ProcessLink::SendMessage | IPC_Message_Name=PBackgroundIDBCursor::Msg_Response]

Categories

(Core :: Storage: IndexedDB, defect, P3)

Product:
Core
Component:
Storage: IndexedDB
Version:
74 Branch
Platform:
Unspecified
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: yoasif, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-f9750778-fe43-4420-938a-c65fb0200320.

Top 10 frames of crashing thread:

0 xul.dll mozilla::ipc::ProcessLink::SendMessage ipc/glue/MessageLink.cpp:153
1 xul.dll mozilla::ipc::MessageChannel::Send ipc/glue/MessageChannel.cpp:1024
2 xul.dll mozilla::ipc::IProtocol::ChannelSend ipc/glue/ProtocolUtils.cpp:477
3 xul.dll mozilla::dom::indexedDB::PBackgroundIDBCursorParent::SendResponse ipc/ipdl/PBackgroundIDBCursorParent.cpp:100
4 xul.dll mozilla::dom::indexedDB::`anonymous namespace'::Cursor<mozilla::dom::IDBCursorType::ObjectStore>::CursorOpBase::SendSuccessResult dom/indexedDB/ActorsParent.cpp:26990
5 xul.dll mozilla::dom::indexedDB::`anonymous namespace'::TransactionDatabaseOperationBase::SendPreprocessInfoOrResults dom/indexedDB/ActorsParent.cpp:22707
6 xul.dll mozilla::dom::indexedDB::`anonymous namespace'::TransactionDatabaseOperationBase::Run dom/indexedDB/ActorsParent.cpp
7 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1220
8 xul.dll NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
9 xul.dll mozilla::ipc::MessagePumpForNonMainThreads::Run ipc/glue/MessagePump.cpp:332

This crash appears to have reappeared, it was previously reported as Bug 1597211. 12 crashes across 9 installs in the last week.

See Also: → 1597211

Hi Simon, can you take a look here?

Flags: needinfo?(sgiesecke)
Priority: -- → P2

The crash reports do not allow to see how many records are contained in the message to be sent. If it's only a single record, then everything works as expected. If there are multiple records, then there is some issue in how the size calculation is done. We could add crash annotations to get more detailed information on this. However, given the very low volume of such crashes, I am not sure if it is worthwhile to investigate this deeply.

Flags: needinfo?(sgiesecke)
Priority: P2 → P3

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3
Crash Signature: [@ mozilla::ipc::ProcessLink::SendMessage | IPC_Message_Name=PBackgroundIDBCursor::Msg_Response] → [@ mozilla::ipc::MessageChannel::Send | mozilla::ipc::IProtocol::ChannelSend | IPC_Message_Name=PBackgroundIDBCursor::Msg_Response ] [@ mozilla::ipc::ProcessLink::SendMessage | IPC_Message_Name=PBackgroundIDBCursor::Msg_Response]

Update, after a lot of fiddling, I got it working.

Unfortunately I can't addon I disabled to fix it - since I did a lot of testing on and off.

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.