Create a static analysis to determine callers which hold on to an XPCOM interface without addrefing it and call more than one function on it

NEW
Unassigned

Status

()

Core
Rewriting and Analysis
5 years ago
5 years ago

People

(Reporter: Away for a while, Unassigned)

Tracking

(Blocks: 1 bug, {sec-want})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
See bug 772282 as an example of a crash resulting in this.  If the caller doesn't AddRef, it cannot be sure that the first function call which takes the interface pointer as an argument won't destroy the object, so the subsequent calls on that are going to be unsafe.

Updated

5 years ago
Blocks: 430328

Updated

5 years ago
Keywords: sec-want
You need to log in before you can comment on or make changes to this bug.