244018 - If you put an string too long (In my computer 5100 characters) reboot the computer

Status: RESOLVED EXPIRED

(SeaMonkey :: Location Bar, defect)

Description

[Rafael]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040514

It's too easy in the location bar write:
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA... (51000 characters)

The computer are freezed few seconds then the screen is black and change a low
resolution.

Reproducible: Always
Steps to Reproduce:
1. Open mozilla ;-)
2. Cut/copy a long string(for ex. 1000 characters)
3. Then paste it in the location bar until it crash

Actual Results:  
Mozilla is (and all the computer) is freezed then few seconds after the screen
is blank and change a low resolution( 640x480 with 16 colors!!!!)

Expected Results:  
A 404 error, page not found :-)

Comment 1

[Jo Hermans]

WFM, but I'm seeing bug 237085 and bug 35229 instead.

Comment 2

[Frank Wein [:mcsmurf]]

wfm current cvs trunk on win2k
Reporter: Is your graphic card driver up-to-date? What graphiccard and driver
version do you have?

Comment 3

[Rafael]

(In reply to comment #1)
> WFM, but I'm seeing bug 237085 and bug 35229 instead.

At 10000 characters my location bar is converted in a blank line (maybe(In reply
to comment #2)
> wfm current cvs trunk on win2k
> Reporter: Is your graphic card driver up-to-date? What graphiccard and driver
> version do you have?

My graphic card is an Intel Extreme graphics ver. 6.13.01.3442

I test the same in my linux (SuSE 9.0 with the same graphic card, kernel 2.4.6
updated and KDE 3.2.1, Mozilla 1.6) but it didn't crashed, it only converted my
location bar in a black line

Comment 4

[Bernard Alleysson]

reporter, can you post one talback ID for the crash ?

Comment 5

[Rafael]

(In reply to comment #4)
> reporter, can you post one talback ID for the crash ?

When I exploit mozilla my PC make a file called mini-date.dmp with a size of 64KB.
If you want a can up it else if don't worry can you explain how can do a talback
ID? :-)

Comment 6

[Bernard Alleysson]

Talkback is an application that reports crash information back to mozilla.org
It's talkback.exe located in the "components" subfolder of your mozilla setup.
So basicly for every crash talback comes in, you fill the information, click
send, then run "talkback.exe", select the incident, copy, then paste into the
bug. Of course you have to enable talkback if it's disabled, just look at the
talback "talkback.exe" application menus. HTH.

Comment 7

[Rafael]

(In reply to comment #6)
> Talkback is an application that reports crash information back to mozilla.org
> It's talkback.exe located in the "components" subfolder of your mozilla setup.
> So basicly for every crash talback comes in, you fill the information, click
> send, then run "talkback.exe", select the incident, copy, then paste into the
> bug. Of course you have to enable talkback if it's disabled, just look at the
> talback "talkback.exe" application menus. HTH.
> 

Thank Bernard, it help me too much. I don't knew this program.
I try to exploit it again with the agent loaded but it don't detect any incident
although my computer was freezed (few seconds) then changed a low resolution.
After I tried to change a normal resolution (1024x768x32) but I couldn't.
Maybe, I'm writing in memory area of the graphic card (in MSDOS begin at Axxx in
 Windows XP I don't know)

Comment 8

[Adam Hauner]

Rafael: Any new information? Did you get TalkBack incident id?

Comment 9

[Gervase Markham [:gerv]]

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 10

[Gervase Markham [:gerv]]

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.