Closed Bug 562046 Opened 15 years ago Closed 8 years ago

[OOPP] No plugin crash UI when the plugin crashes before NPP_New

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: glandium, Unassigned)

Details

When the flash plugin can't load libcurl.so.3, libcurl.so.4, libcurl-gnutls.so.3, and libcurl-gnutls.so.4, it crashes. In such cases, the place where the plugin would be displayed only displays black, and not the expected "plugin crashed" overlay.
I believe this is because the crash happens during NP_Initialize, or at least sometime before NPP_New. This means that we don't associate the crash with any particular instance, so the plugin-crashed notifications for instances which are going to be initialized shortly aren't sent to the chrome observers.
Fixed in 10.1.53.64
Assignee: nobody → jet
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
This bug is about OOPP support, not flash itself (though it's nice that flash is fixed).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: jet → nobody
Summary: [OOPP] No plugin crash UI when the flash plugin crashes because of libcurl missing → [OOPP] No plugin crash UI when the plugin crashes before NPP_New
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 8 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.