Bug 110303 - mozilla crashes on google search for qmake
mozilla crashes on google search for qmake
Product: Fedora
Classification: Fedora
Component: mozilla (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Christopher Blizzard
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-11-17 21:56 EST by Martin Flack
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-11-20 23:35:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
lynx dump output of what mozilla is choking on (14.40 KB, text/html)
2003-11-17 21:58 EST, Martin Flack
no flags Details

  None (edit)
Description Martin Flack 2003-11-17 21:56:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
Mozilla crashes due to something on the results page of a Google
search for "qmake".

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Launch Mozilla.
2. Go to www.google.com
3. Type "qmake" in the search box and press Enter.
2. Open Mozilla search sidebar.
3. Type "qmake" in the search box and press Enter.

Actual Results:  Mozilla crashes.

Expected Results:  Should display the web page.

Additional info:
Comment 1 Martin Flack 2003-11-17 21:58:53 EST
Created attachment 96037 [details]
lynx dump output of what mozilla is choking on

Made using "lynx -dump -source" at the same time as mozilla was found to be
crashing, so that we could preserve the Google result page. If I navigate to
this file locally, mozilla also crashes.
Comment 2 petrosyan 2003-11-20 13:11:52 EST
run System Tools / Red Hat Network
and update your system to the latest mozilla-1.4.1-18
see if it still crashes.
Comment 3 Martin Flack 2003-11-20 23:35:00 EST
No it works after that update. Thanks!

Note You need to log in before you can comment on or make changes to this bug.