Closed Bug 534791 Opened 15 years ago Closed 15 years ago

[e10s] parent crash unloading plugin [@ mozilla::plugins::PluginInstanceParent::Destroy()]

Categories

(Core Graveyard :: Plug-ins, defect)

x86
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 530007

People

(Reporter: benjamin, Unassigned)

References

Details

(Keywords: crash)

Crash Data

Browsing youtube, crashing in the parent:

>	xul.dll!mozilla::plugins::PluginInstanceParent::Destroy()  Line 93 + 0x8 bytes	C++
 	xul.dll!mozilla::plugins::PluginModuleParent::NPP_Destroy(_NPP * instance=0x07185b08, _NPSavedData * * save=0x0026f3a4)  Line 173	C++
 	xul.dll!nsNPAPIPluginInstance::Stop()  Line 1019 + 0x51 bytes	C++
 	xul.dll!DoStopPlugin(nsPluginInstanceOwner * aInstanceOwner=0x07401d88, int aDelayedStop=0x00000000)  Line 2172	C++
 	xul.dll!nsStopPluginRunnable::Run()  Line 2219 + 0x13 bytes	C++
 	xul.dll!nsThread::ProcessNextEvent(int mayWait=0x00000000, int * result=0x0026f494)  Line 527 + 0x19 bytes	C++

Here, `object` is 0xdddddddd which means freed memory on Windows. This likely means that the PluginInstanceParent is already freed. I'm trying to think what kind of race would leave an invalid PluginInstanceParent hanging around; nothing comes to mind right now.
Severity: normal → critical
Keywords: crash
Summary: [e10s] parent crash unloading plugin → [e10s] parent crash unloading plugin [@ mozilla::plugins::PluginInstanceParent::Destroy()]
The only other thing which can destroy PluginInstanceParent other than NPP_Destroy itself is: ActorDestroy (plugin crash, but I don't think that's happening here) or NP_Shutdown. It's illegal to call NPP_Shutdown after NP_Shutdown, so I'm stumped. Maybe need logging if this keeps happening.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Crash Signature: [@ mozilla::plugins::PluginInstanceParent::Destroy()]
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.