Closed
Bug 281697
Opened 20 years ago
Closed 19 years ago
Extremely long url crashes not only in firefox, but complete xorg-x11
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: marcospringer, Assigned: blizzard)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 When entering an extremely long link firefox crashes up and not only that but also xorg-x11 crashes, the system itself does not hang. Tried to reproduce on a windows xp machine and nothing happens, seems only to happen on the linux machine. Reproducible: Always Steps to Reproduce: 1. Enter a very very very long url in the adress bar, starting with http://[valid adres]/[very very long url] Actual Results: Screen scrambled just like a real good crash and the computer responded to nothing from the keyboard/mouse. Logged in remotely with ssh and killed xorg-x11 and restarted it, firefox works fine to except on the extremely long url. Expected Results: Popup an information window that the filled in URL could not be found or perhaps is (way) too long. Running the normal install from the website, not compiled from source. The url i was testing it on was located on an linux machine with apache-2.0.53 No themes installed, extension for download statusbar installed. Computer config: athlon-xp machine running gentoo linux 2004.3 using kernel 2.6.10 using nvidia drivers for g-force ti4200 in dual display mode using xorg-x11 6.8.0
Assignee: firefox → blizzard
Component: General → Widget: Gtk
Product: Firefox → Core
QA Contact: general → ian
Whiteboard: DUPEME
Version: unspecified → 1.7 Branch
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
I can confirm this bug. I'm running SeaMonkey 1.0.3 Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060902 SeaMonkey/1.0.3. Reproducable: Most times, but sometimes I just displays me an error message from dante. Actually my X-server restarts automatically, apart from that I have the same symptons. Kernel: 2.6.17-gentoo-r4 Xorg: 7.0-r1 Nvidia: 1.0.8762-r1
You need to log in
before you can comment on or make changes to this bug.
Description
•