Closed Bug 307398 Opened 19 years ago Closed 19 years ago

crash with Xorg if I search the word fesep in http://www.google.fr

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 244340

People

(Reporter: rpnpif, Unassigned)

References

()

Details

Attachments

(2 files, 1 obsolete file)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.7.11) Gecko/20050729
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.7.11) Gecko/20050729

mozilla 2> mozilla.log
I open : http://www.google.fr/
I search the keyword : feder.
Xorg crashed

$ cat mozilla.log
Gdk-ERROR **: Fatal IO error 104 (Connection reset by peer) on X server :0.0.

Reproducible: Always

Steps to Reproduce:
1.Open the url http://www.google.fr/ in Mozilla
2.Type the word feder in the searching zone of the site.
3.

Actual Results:  
Xorg close and gdm restart.

Expected Results:  
Display the page
http://www.google.fr/search?hl=fr&ie=ISO-8859-1&q=feder&btnG=Recherche+Google&meta=
Sorry, i make an error : it is the fesep word which is searched and which make
crashed.
URl fixed.
Summary: crash with Xorg if I search the word feder in http://www.google.fr → crash with Xorg if I search the word fesep in http://www.google.fr
Attached file testcase (obsolete) —
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.9a1) Gecko/20050907 SeaMonkey/1.1a
I'm on windows, so I don't crash (here ;-).
In that page is one link not encoded in ISO-8859-1, and I assume this font
problem is breaking your Mozilla. I isolated this in this testcase, but don't
know, if that crashes or not. Please test.

<p class="g"><!--m--><span class="w"><font
 size="-2"><b>[PDF]</b></font></span>
<a href="http://web.mse.kth.se/drweb/abstracts/malin_ekroth.pdf"
 onmousedown="return
rwt(this,'res','4','')">&cent;&iexcl;&curren;&pound;&brvbar;&yen;&uml;&sect;
&copy; &iexcl; "!# &curren;
"&iexcl;&curren;&copy;%$&amp;&sect;' )(0&copy;
12&copy; 3&copy;%&yen;4(0&pound;&brvbar;&iexcl;
56&sect;7&yen;6&copy;%$</a>
Thank you for your help.

I paste your extract in a source page of composer. Then I saved in a file and
open this in the browser. But no crash is happened with this. Same thing with an
html editor in mode text.
are you using a gtk1 or gtk2 build?  If you don't know, load about:buildconfig

you might be seeing bug 244340
Attached file testcase #2
I made the first testcase using nVu, and now see a doctype was added, and the
source looks different to the original.
This time I used pn on a download of the html, but also don't know if the
garbage characters are reproduced originally.
Attachment #195181 - Attachment is obsolete: true
(In reply to comment #3)
> Thank you for your help.
> 
> I paste your extract in a source page of composer. Then I saved in a file and
> open this in the browser. But no crash is happened with this. Same thing with an
> html editor in mode text.

Did you copy&paste from my comment 2? Then it can't work. You should have tested
testcase attachment 195181 [details]. This isn't quite the same as the original, so I
added testcase #2 Attachment 195283 [details]. Please test this. 
(In reply to comment #4)
> are you using a gtk1 or gtk2 build?  If you don't know, load about:buildconfig
> 
> you might be seeing bug 244340

about:buildconfig

Build platform
target
i686-pc-linux-gnu

Build tools
Compiler 	Version 	Compiler flags
gcc 	gcc version 3.2.3 	-Wall -W -Wno-unused -Wpointer-arith -Wcast-align
-Wno-long-long -pedantic -pthread -pipe
c++ 	gcc version 3.2.3 	-fno-rtti -fno-exceptions -Wall -Wconversion
-Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy
-Wno-non-virtual-dtor -Wno-long-long -pedantic -fshort-wchar -pthread -pipe
-I/usr/X11R6/include

Configure arguments
--enable-application=suite --enable-extensions=default,irc,tasks,negotiateauth
--disable-tests --disable-debug '--enable-optimize=-O2 -gstabs+'
--without-system-nspr --without-system-zlib --without-system-jpeg
--without-system-png --without-system-mng --without-system-mng --enable-crypto 
(In reply to comment #6)

> Did you copy&paste from my comment 2? Then it can't work.

Yes I think so.

> This isn't quite the same as the original, so I
> added testcase #2 Attachment 195283 [details] [edit]. Please test this. 

With this attachment, I can confirm the bug. Mozilla crashes with the X server.
Yes, this attachment has the problem.
Attached file reduced testcase
http://validator.w3.org/check?uri=https%3A%2F%2Fbugzilla.mozilla.org%2Fattachment.cgi%3Fid%3D195283


Validator about testcase 2:

Byte-Order Mark found in UTF-8 File.

    The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known to cause
problems for some text editors and older browsers. You may want to consider
avoiding its use until it is better supported.

Line 48 column 28: non SGML character number 129.
...
Line 49 column 84: non SGML character number 158.

in total there are 20 errormessages about non SGML characters.

Use http://validator.w3.org/ on this attachment to see the messages.
Your about:buildconfig confirms you have a gtk1 build.  You can workaround the
xorg bug by disabling xfs (add the font directories directly to your xorg.conf
instead) or use a gtk2 build.

*** This bug has been marked as a duplicate of 244340 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: