24251 - In IFRAME, referencing a unknown format in SRC will cause a freeze

Status: VERIFIED FIXED

(Core :: Layout, defect, P2)

Description

[Chris Petersen]

build: Apprunner
version: 2000011408
Platform: Mac
Other Platforms: Have yet to check on Linux or Windows

Expected Results: Apprunner should display the empty iframe (since the format is
not supported) and not freeze.

What I got: Opening the attached file results in a freeze.

Steps to reproduce:

1) Open the attached file in apprunner.(source reference is .pdf)
2) The window is balck and application freezes.

Comment 1

[Chris Petersen]

Step 2 should be:

The window is blank and the applicaton freezes.

Comment 2

[Chris Petersen]

Attachment: Iframe using src with a unsupported format

Comment 3

[rickg]

eric -- I think you own iframe, right? Here's an odd problem for you.

Comment 4

[Chris Petersen]

This problem happens when the src file is local on the hard drive.

Here are updated steps to reproduce the bug:

1) Download the test case to drive.
2) On the computer, create a directory ( at the same root as the test case)
called "images"
3) Place a file (save in a unsupported format such as .pdf) inside this folder.
4) Update the src to reflect the file's location.
5) Attempt to open the test case in Apprunner.
6) The application should appear to freeze.

Comment 5

[Chris Petersen]

This problem occurs on all platforms.

Comment 6

[Eric Pollmann]

This appears to be a plugin problem and not an iframe problem.

You can remove iframes from the equation entirely by just trying to visit the
pdf url directly:

http://blueviper/frames/images/test.pdf

This also causes a freeze for me, but I got this printed out to the console on
the way:

PluginViewerImpl::StartLoad: content-type=application/pdf
InstantiateFullPagePlugin for application/pdf
IsPluginFile(/builds/pollmann/mozilla/dist/bin/plugins/npsimple.o)
LoadPlugin() /builds/pollmann/mozilla/dist/bin/plugins/npsimple.o returned 0
IsPluginFile(/builds/pollmann/mozilla/dist/bin/plugins/libflashplayer.so)
LoadPlugin() /builds/pollmann/mozilla/dist/bin/plugins/libflashplayer.so
returned 0

Giving this to Andre, the plugins guru.

(Note that *this* url worked okay though and is very similar as I have not
 plugins for either postscript or acrobat files:
  http://blueviper/frames/images/framesetframereflow.ps)

Comment 7

[leger]

This is blocking QA's testing...set to Blocker
The bug's impact is that opening any file format that requires spawning an 
external app, i.e. Acrobat Reader for PDF files, causes the browser to freeze.

Comment 8

[leger]

Putting on PDT+ radar for beta1.

Comment 9

[ekrock's old account (dead)]

Let's clarify something on this bug: when we visit a PDF URL such as 
http://blueviper/frames/images/test.pdf, are we causing the plug-in to execute 
in "embedded plug-in mode" (supported for beta1) or in "helper app mode" 
(typically, executing as a standalone app in its own window, which is out for 
beta1).

I tested this in Nav4.7, and (pardon my ignorance here) was uncertain about 
which mode Acrobat was operating in when I visited the URL 
http://blueviper/frames/images/test.pdf. Because I saw the splash screen, it 
seemed like Acrobat was operating in "helper app mode," but the PDF file was 
displayed within the browser content area, which confused me.  I suspect that 
what's happening here is that Acrobat is indeed running in "helper app mode" 
here but that the contents are displayed within the browser window content area 
for some reason.

I'm clearer on this distinction in the RealPlayer case where EMBED within an 
HTML file causes the plug-in to run in "plug-in mode," but an <A HREF="foo.ram"> 
link to a .ram file causes RealPlayer to launch as a helper app and play the 
file in its own RealPlayer top-level OS window.

*Definitely*, Mozilla should not freeze on visiting any URL (plug-in or not); 
such behavior is equivalent to a crash in severity and generally beta1 caliber 
for that reason.

But once that problem is taken care of, for beta1 we're only supporting 
"embedded plug-in mode" use of plug-ins, not the "helper app mode."

Comment 10

[av (gone)]

I do not see freeze or crash. 

Comment 11

[av (gone)]

I assume that original problem has been fixed. petersen, could you please check 
thi one on Unix and Mac?

Comment 12

[Chris Petersen]

I don't get the freeze problem with the  Linux and Mac builds either (Feb 21).

Comment 13

[av (gone)]

Marking fixed then.

Comment 14

[Chris Petersen]

Verfied fixed in the Feb 21 build.

Comment 15

[Heikki Toivonen (remove -bugzilla when emailing directly)]

SPAM. HTML Element component deprecated, changing component to Layout. See bug
88132 for details.