Closed Bug 1319693 Opened 8 years ago Closed 8 years ago

Crash in mozilla::dom::indexedDB::BlobOrMutableFile::AssertSanity

Categories

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

Unspecified
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1313176
Tracking Status
firefox52 - affected
firefox53 --- affected

People

(Reporter: bbouvier, Unassigned)

References

Details

(Keywords: crash)

Crash Data

[Tracking Requested - why for this release]: devtools issue with wasm modules in indexeddb

This bug was filed from the Socorro interface and is 
report bp-7e08ff82-579d-4058-90a4-8d5f72161123.
=============================================================

STR:
- Store a wasm module in an indexeddb object store (in a content web page)
- open devtools
- go to the Storage tab (needs to be enabled in settings if it's not there by default)
- click on indexeddb > db name > object store name
- 100% crash repro rate:
bp-7e08ff82-579d-4058-90a4-8d5f72161123
bp-da7423a6-d29d-427a-8836-bdbd82161123
I believe this is basically a dup of bug 1313176, but if we can't fix that bug for 52, then perhaps we can use this bug to just mitigate the assertion by having things fail more gracefully?
Flags: needinfo?(jvarga)
Yes, this is bug 1313176. If we can't fix that bug any time soon, we should add some early bail outs at least.
Flags: needinfo?(jvarga)
asuth said he could take a look.
Priority: -- → P2
(In reply to Andrew Overholt [:overholt] from comment #3)
> asuth said he could take a look.

Oops, I was thinking of bug 1319737. Let's dupe this to bug 1313176.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Let's track bug 1313176 instead of this one for 52
You need to log in before you can comment on or make changes to this bug.