Closed Bug 1411721 Opened 8 years ago Closed 8 years ago

Crash in mozilla::ipc::IProtocol::OtherPid call from asmjscache

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows 10
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1405828
Tracking Status
firefox-esr52 --- affected
firefox56 --- wontfix
firefox57 --- wontfix
firefox58 --- fixed

People

(Reporter: jesup, Assigned: overholt)

Details

(4 keywords, Whiteboard: [adv-main58-])

Crash Data

This bug was filed from the Socorro interface and is report bp-ff2cd2f0-764b-405c-8b0b-8812e0171024. ============================================================= fairly high volume (>130 in the last week) UAF when called from dom::asmjscache::PAsmJSCacheEntryParent::SendOnOpenCacheFile() Appears to have started in 52, but rising strongly in frequency (increased use of e10s I presume).
Group: core-security → dom-core-security
[Tracking Requested - why for this release]: The crash volume is higher on 57 beta than on 56 release despite having a fraction of the users, so something definitely got worse here. Andrew: where does asmcache fit? in the tree it's under DOM, and some of the bugs fixed in that file were in the DOM component, others were in JS. Can you help find the right owner/place for this one? It looks like it's getting worse in 57
Assignee: nobody → overholt
Flags: needinfo?(overholt)
Keywords: regression
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(overholt)
Resetting track flag. We can track for 57 in the duplicate bug.
Whiteboard: [adv-main58-]
Group: dom-core-security
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.