220568 - Run plugins in seperate process, allow them to be killed through Mozilla

Status: RESOLVED DUPLICATE of bug 156493

(Core Graveyard :: Plug-ins, enhancement)

Description

[Brian 'netdragon' Bober]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20030925 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20030925 Firebird/0.7+

When I click on a PDF file, and then acrobat starts loading, I'd like to be able
to stop it by hitting the stop button. I don't know if this is something we can
do -- like end-tasking the plugin or sending it a close signal, but if so, the
ability to stop plugins from loading with the stop button would be nice.

Reproducible: Always

Steps to Reproduce:
Click on a PDF file and try to stop it by hitting stop



How do I get the original enter bug form? This one is annoying.

Comment 1

[Matthias Versen [:Matti]]

I don't think that you can stop the loading. There is only a way to disable a
plugin before you load something that needs it or close it later after it's loaded.

>How do I get the original enter bug form?
You can't without permissions.

Comment 2

[David G King]

I seem to recall an existing bug report dealing with the Java plugin that
requests a Yes/No prompt before loading plugin. Maybe this bug could become part
of that one.

Sorry, can't find bug number.

Comment 3

[Brian 'netdragon' Bober]

> You can't without permissions.

Ahh, that explains it. Doron took them away for no reason the other day.

Comment 4

[Brian 'netdragon' Bober]

Ok, well I've been thinking about this, and it seems that Mozilla kinda freezes
up when you start loading the plugin. It seems like its waiting for something
from, say, Acroread. What if we de-linked Mozilla from the plugin, so that
basically you could use Mozilla as-is, and when the plugin loaded, Mozilla would
send it a message to terminate. Is that possible?

Another thing I just noticed today is that when Acroread crashes, so does
Mozilla. This is sort of along the same lines. Mozilla needs to load its plugins
in a way that protects the Mozilla process.

Comment 5

[Matthias Versen [:Matti]]

That a plugin crashes Mozilla is known and we have a bug for that (search yourself)

Reason : The plugin runs in the same process as Mozilla.

Comment 6

[Brian 'netdragon' Bober]

That was just an offtopic side note though. What I'm talking about is why can't
Mozilla de-link the plugin from the window, hide its window, or whatever, and
then just act as if its back to normal browsing until the plugin has fully
loaded and can be told to terminate?

Comment 7

[Brian 'netdragon' Bober]

I figured out what Acroread is waiting for. It brings up a prompt whether you
are sure you want to exit, but that prompt window is not in the front so you
never see it.

We need plugins in a seperate process, and we need them to be able to be killed
through Mozilla (STOP button with a prompt for plugins loaded into the content
area, maybe?). Changing bug summary to reflect that.

Comment 8

[Matthias Versen [:Matti]]

yes but that's a dupe. Please search yourself and dupe this bug

Comment 9

[Matthias Versen [:Matti]]

*** This bug has been marked as a duplicate of 156493 ***