270997 - crash [@ FOFindTableIndexInternal] when loading a page with specific characters

Status: RESOLVED INVALID

(Core :: Internationalization, defect)

Description

[Roine Gustafsson]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041119 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041119 Camino/0.8+

A certain combination of characters in a page will crash Firefox 0.8. These were
found on a Google result page.

Reproducible: Always
Steps to Reproduce:
1. Google for "82810 xvmc". You get
http://www.google.com/search?q=xvmc+82810&ie=UTF-8&oe=UTF-8
2. Browser crashes

Actual Results:  
Browser crash @ FOFindTableIndexInternal

Expected Results:  
not crash

In case the google page changes, I will attach the complete Google result page.
It also crashes Camino 0.8.2 as well as the latest nightly. It does not crash
Safari, or Textedit.
Camino crashes even if just a few crucial characters is present, saved as a text
file. Firefox crashes only if I open the complete result page in html.
Both Camino and Firefox crashes in the same call, FOFindTableIndexInternal.

Comment 1

[Roine Gustafsson]

Attachment: Result page from google search. Will crash both Firefox and Camino.

Comment 2

[Roine Gustafsson]

Attachment: Snippet from googlepage.html. Will crash camino, but not Firefox.

Comment 3

[Roine Gustafsson]

Attachment: Mac OS X crash log

Comment 4

[Uri Bernstein]

WFM on both
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107
Firefox/1.0
and
Camino 2004082512 (v0.8.1)

OS X 10.3.7

Comment 5

[Uri Bernstein]

Also WFM on the latest FF trunk build:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a5) Gecko/20041119
Firefox/0.9.1+

My Camino version is actually very old, so you can ignore the "WFM on Camino"
from my previous comment.

Comment 6

[Asaf Romano (gone)]

Reporter: can you provide talkback id?

WFM: Camino 2004112008 (v0.8+)

Comment 7

[Roine Gustafsson]

I can no longer reproduce this. Works both in Camino and Firefox now.
I'm speculating the error might have been a broken font file on my system.