crash in RtlpAllocateHeapRaiseException | RtlpAllocateHeapInternal | RtlAllocateHeap | F676319623_______________________________________________

RESOLVED INCOMPLETE

Status

External Software Affecting Firefox
Flash (Adobe)
--
critical
RESOLVED INCOMPLETE
2 years ago
2 years ago

People

(Reporter: marco, Unassigned)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

2 years ago
This bug was filed from the Socorro interface and is 
report bp-619c6387-4b92-48bc-b9c6-35cc42160426.
=============================================================

Filing this bug because there is no associated report to that signature yet.

Looks like an OOM crash in the Flash process.

Comment 1

2 years ago
Version and milestone values are being reset to defaults as part of product refactoring.
Version: 20.x → unspecified

Comment 2

2 years ago
Marco, do you have specific STR or is this a topcrash? Otherwise we normally don't track.
Flags: needinfo?(mcastelluccio)
(Reporter)

Comment 3

2 years ago
#37 according to https://crash-analysis.mozilla.com/rkaiser/2016-05-01/2016-05-01.firefox.release.explosiveness.html, but I can't find it on https://crash-stats.mozilla.com/topcrashers/?product=Firefox&version=46.0.
Flags: needinfo?(mcastelluccio)

Comment 4

2 years ago
That's because you didn't click the "plugin" option (it looks at browser crashes only by default).

It's #7 on plugin topcrashes.

Unfortunately this is not really actionable. We're either out of memory or address space, or the Flash heap is corrupted. But without specific STR I'm just going to close this INCOMPLETE.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.