Closed Bug 1337000 Opened 7 years ago Closed 3 years ago

[e10s-multi] Page content does not appear after killing the plugin

Categories

(Core Graveyard :: Plug-ins, defect, P3)

54 Branch
x86_64
Windows 7
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: over68, Unassigned)

References

Details

(Whiteboard: [e10s-multi:-])

Steps to reproduce:

1. Go to https://dl.dropboxusercontent.com/u/95157096/85f61cf7/fe80383b.swf.
2. Open this page in a new tab https://bugzilla.mozilla.org/attachment.cgi?id=8671317.
3. When view the notification, click on "Stop It".

See https://dl.dropboxusercontent.com/u/95157096/85f61cf7/z1abam45dj.mp4


Actual results:

Can not kill the plugin and display the page content.
Blocks: e10s-multi
blinky, I don't see any evidence in the video that you ever killed the plugin. It looks like you're interacting with the browser slow-script dialog, but that isn't the same as the hung-plugin dialog.

I agree that there's a problem here, though, since it looks like you never saw the hung-plugin dialog.

Did you write the SWF file here, or get it from somewhere? Can I see the source of it?
Flags: needinfo?(over68)
(In reply to Benjamin Smedberg [:bsmedberg] from comment #1)
> blinky, I don't see any evidence in the video that you ever killed the
> plugin. It looks like you're interacting with the browser slow-script
> dialog, but that isn't the same as the hung-plugin dialog.

When click on "Stop It", the Flash process disappear from the task manager.

See https://dl.dropboxusercontent.com/u/95157096/85f61cf7/ecwkxvj8fe.mp4


> Did you write the SWF file here, or get it from somewhere? Can I see the
> source of it?

I found the SWF file by the Google search, I don't remember the source.
Flags: needinfo?(over68)
Whiteboard: [e10s-multi:?]
Whiteboard: [e10s-multi:?] → [e10s-multi:-]
Priority: -- → P3
Resolving as wont fix, plugin support deprecated in Firefox 85.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.