Opening this causes an incredible number of empty tabs to be opened until the browser process is killed.

VERIFIED DUPLICATE of bug 218257

Status

Core Graveyard
File Handling
--
critical
VERIFIED DUPLICATE of bug 218257
12 years ago
a year ago

People

(Reporter: marcrios, Unassigned)

Tracking

1.8 Branch
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2

Closing the window does not terminate the problem; a new window with many more tabs is created as soon as the previous one is closed.

I'm sorry to report that this is an International Obsfucated C Contest winner (the page that sets off the error). But I figured that if a c file could cause these problems, there may be a problem with firefox executing code it sees in the browser window -- a potential security hole.

Good luck!



Reproducible: Always

Steps to Reproduce:
1.Open link in new tab
2.Watch as millions of tabs are created.

Actual Results:  
The problem is that if I reproduce it now, my browser will crash and I will not be able to file the bug. 


I wasn't using any special theme. My extensions were adblock and flashblock.

Comment 1

12 years ago
Guessing this is a File Handling bug.

WFM, Mac trunk.
Assignee: nobody → file-handling
Component: Tabbed Browser → File Handling
Product: Firefox → Core
QA Contact: tabbed.browser → ian
Version: unspecified → 1.8 Branch

Comment 2

12 years ago
For example, this might be a dup of bug 215554.
Hmm, Firefox doesn't open this directly.  Did you choose to open it in Firefox?  That yields... unpleasant results (infinite recursion, since we try to open the URL in an external app if we go down that path....
(Reporter)

Comment 4

12 years ago
(In reply to comment #3)
> Hmm, Firefox doesn't open this directly.  Did you choose to open it in Firefox?
>  That yields... unpleasant results (infinite recursion, since we try to open
> the URL in an external app if we go down that path....
> 

Yes, I tried to open it in firefox. I wanted to look at it like I would a text file. I was able to see other source code files on the website without problems. 

I simply clicked on it. Is it significant that I have firefox set up to open pages in tabs if their HTML tries to open a new window?
If the file is sent with a MIME type Firefox doesn't understand, (in this case text/x-csrc) selecting Firefox as the helper app (as mentioned in comment 4) will cause the loop described.


*** This bug has been marked as a duplicate of 218257 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → DUPLICATE

Updated

12 years ago
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.