Closed Bug 760132 Opened 9 years ago Closed 9 years ago
Parent may use uninitialized m Frame Element pointer
It's possible (likely) that there's no way to trigger this in current builds, but this is bad enough that I didn't want to file a public bug. Patch in a moment.
Summary: TabChild may use uninitialized mFrameElement pointer → TabParent may use uninitialized mFrameElement pointer
We still ship this code.
Attachment #628754 - Flags: review?(jones.chris.g) → review+
Target Milestone: --- → mozilla15
Assignee: nobody → justin.lebar+bug
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
What is this code used for? Would it affect regular firefox builds (e.g. ESR) or can we skip it for those. Would Fennec Native need it?
(In reply to Daniel Veditz [:dveditz] from comment #5) > What is this code used for? Would it affect regular firefox builds (e.g. > ESR) or can we skip it for those. Would Fennec Native need it? This bug doesn't affect builds which don't spin up OOP frames. So regular Firefox, ESR, and Fennec Native are unaffected.
You need to log in before you can comment on or make changes to this bug.