Closed
Bug 1202067
Opened 9 years ago
Closed 3 years ago
Size limit on IndexedDB Blob storing
Categories
(Core :: Storage: IndexedDB, defect, P5)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
platform-rel | --- | - |
People
(Reporter: azakai, Unassigned)
Details
(Whiteboard: [games:p1][platform-rel-Games])
Attachments
(1 file)
772.96 KB,
application/zip
|
Details |
The attached testcase attempts to store a 300MB Blob in IndexedDB. It fails silently on Firefox, the JS console shows
IndexedDB UnknownErr: ActorsParent.cpp:13734
IndexedDB UnknownErr: ActorsParent.cpp:12255
It works in Chrome. It also works if I reduce the size of the file, looks like around 256MB or so is fine.
Whiteboard: [games:p1]
Updated•9 years ago
|
Whiteboard: [games:p1] → [games:p1][platform-rel-Games]
Updated•9 years ago
|
platform-rel: --- → ?
Comment 1•9 years ago
|
||
Noting that this is a critical blocker for our upcoming fully IndexedDB based filesystem in Emscripten asm.js/wasm games.
Updated•9 years ago
|
platform-rel: ? → -
Comment 3•9 years ago
|
||
I can reproduce the crash with a simple test and 300 MB blob. Investigating...
Flags: needinfo?(jvarga)
Comment 4•9 years ago
|
||
So here's console output:
Hit MOZ_CRASH(IPC message size is too large) at /Users/varga/Sources/Inbound/ipc/glue/MessageLink.cpp:142
#01: mozilla::ipc::PBackgroundChild::SendPBlobConstructor(mozilla::dom::PBlobChild*, mozilla::dom::BlobConstructorParams const&)[/Users/varga/Sources/Inbound/obj-ff-dbg/dist/NightlyDebug.app/Contents/MacOS/XUL +0x695a0f]
and relevant code:
void
ProcessLink::SendMessage(Message *msg)
{
if (msg->size() > IPC::Channel::kMaximumMessageSize) {
#ifdef MOZ_CRASHREPORTER
CrashReporter::AnnotateCrashReport(NS_LITERAL_CSTRING("IPCMessageName"), n
CrashReporter::AnnotateCrashReport(NS_LITERAL_CSTRING("IPCMessageSize"), n
#endif
MOZ_CRASH("IPC message size is too large");
}
...
}
I also tried to open the attached test and I got the same crash, so I believe this is the same issue as in bug 1274075.
Updated•7 years ago
|
Priority: -- → P5
Comment 5•3 years ago
|
||
Fixed in 2016-12-23 nightly, somehow a little bit after bug 1274075.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•