Closed
Bug 1551929
Opened 5 years ago
Closed 5 years ago
Connection::ExecuteAsync seems to make assumptions that may not hold
Categories
(Toolkit :: Storage, defect)
Toolkit
Storage
Tracking
()
RESOLVED
FIXED
mozilla68
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
Details
Attachments
(1 file)
The code gets an array of mozIStorageBaseStatement and does this:
nsCOMPtr<StorageBaseStatementInternal> stmt =
do_QueryInterface(aStatements[i]);
and then assumes stmt
is not null. But there's nothing guaranteeing that. In particular, mozIStorageBaseStatement is not builtinclass, so the caller could be passing a JS implementation.
I suspect that mozIStorageBaseStatement (and mozIStorageAsyncStatement and mozIStorageStatement) should be builtinclass, right?
Flags: needinfo?(bugmail)
Comment 1•5 years ago
|
||
Yes. All mozIStorage interfaces should be builtinclass.
Flags: needinfo?(bugmail)
Assignee | ||
Comment 2•5 years ago
|
||
Pushed by bzbarsky@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/41f28d23024e Mark some storage interfaces builtinclass, since we assume there are no JS implementations already. r=asuth
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Updated•5 years ago
|
Assignee: nobody → bzbarsky
You need to log in
before you can comment on or make changes to this bug.
Description
•