80931 - Opening a large (4.5Meg) tiff file using PowerDesk to select Moz0.9 creates windows/pages continously.

Status: VERIFIED FIXED

(SeaMonkey :: UI Design, defect)

Description

[David Wilson]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9) Gecko/20010505
BuildID:    2001050515


With a number of windows of Moz already running, attempting to view a large tiff
format file with Moz 0.9 invoked by filehandler PowerDesk creates pages
continuously but does not display any of them correctly.

Like cancer, the creation of new windows/pages is tough to stop and Control Q
finally was successful.  Still, it took about two minutes to clear the twenty or
thirty windows before they all quit on my 512Meg RAM computer.

Doing the same in MS Explorer produces a single window/page but then Explorer
wanted a Quicktime plugin to display the tiff file.  I cancelled the plugin
install so can't say whether it would have successfully displayed the file or not.

Hope this helps. 

Reproducible: Always

Comment 1

[timeless]

moz doesn't natively handle TIFFs. Unknown Content Handler => law.

Comment 2

[Boris Zbarsky [:bzbarsky]]

please try a new build.  The May 5 builds had this infinite-window problem for
some unknown content types.

Comment 3

[sairuh (rarely reading bugmail)]

terri, d'you encounter this?

Comment 4

[Terri Preston]

Reporter, could you attach the file you are using?

Comment 5

[Terri Preston]

Attachment: Image that causes nightmare

Comment 6

[Terri Preston]

Attachment: Okay, try this zip file

Comment 7

[Terri Preston]

Confirming, this is scarey behavior

Comment 8

[kmike]

confirming, using linux 2001051621 nightly build.
i see this behaviour at this url:
http://www.tolkien.ru/pictures/maps/ut/whole.tif
which is only 40k in size.
please, set OS->all.

Comment 9

[kmike]

By the way, I'm getting these in console when spawning windows:
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
Error loading URL http://www.tolkien.ru/pictures/maps/ut/whole.tif : 2152398850
...

Comment 10

[dcary]

Confirming. New (blank) mozilla windows continuously open on my
Mozilla 0.9.1 build 20010607 running on Win98.
This happens with every ``.tif'' file I've tested (all 3 of them).

If I just click the links mentioned at Bug#:80931,
Mozilla does the right thing -- since it doesn't recognize TIFF format, it gives
the ``What should Mozilla do with this file ?'' dialog, and I can save it to disk.
(The file looks OK in an image viewer program).

But if I use ``File | Open'' to select a TIFF file on my hard drive, or
drag-and-drop the file onto Mozilla, I get a wierd cascade of new windows
continuously being created. (CTRL+ALT+DEL to get the Close Program dialog box,
and I can usually stop it).

Comment 11

[Bill Law]

I can recreate the problem (the problem opening a local .tif file creating
umpteen windows) in Netscape6.1.  But it works OK with trunk (or mozilla0.9.4
branch) builds.

Comment 12

[sairuh (rarely reading bugmail)]

terri et al., do i need PowerDesk to test this? [sorry for the delay in asking.]

Comment 13

[sairuh (rarely reading bugmail)]

i can open up the attachment 34789 [details] when specifying gimp on linux and graphic
converter on mac 10.1. i don't get the infinite window problem, either. alas, i
don't have an app on my winNT box that'll handle it. but, i'll vrfy this as
fixed. if it's still an issue, tho', do reopen.

tested using 2001.11.01.12 on linux and 2001.10.31.13 on mac 10.1.