265890 - Segmentation fault when trying to view eweek's site

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Eamonn Sullivan]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

Tried to view eweek's front page (http://www.eweek.com) causes the browser to
quit on Ubuntu (Warty release, a Debian-based distro). I'm using the Mozilla
binaries installed straight from mozilla.org install package. Installed it just
today (24/10/04). 

Reproducible: Always
Steps to Reproduce:
1. start Firefox
2. type www.eweek.com in the address bar
3.

Actual Results:  
Browser closes with a segmentation fault. 

Expected Results:  
display eweek's web site. 

This is a clean install of Ubuntu (just yesterday) that's been made up-to-date
with apt-get. I uninstalled the firefox 0.9.3 that comes with it and installed
the firefox 1.0 preview from mozilla.org in /usr/local.

Comment 1

[Eamonn Sullivan]

This appears to happen only when using 256 colours and with the latest flash
plugin. 

Comment 2

[Richard Lloyd]

Using Firefox 1.0.3 on Linux x86 (Fedora Core 2) with a 1280x1024x16-bit
display, *no* Flash plug-in (confirmed via about:plugins) and starting with
"firefox --safe-mode" to disable all extensions/themes, I still get this crash
when going to http://www.eweek.com/ so I don't think it's the Flash plug-in or
256-colour mode to blame here. I didn't think it was Flash because I use the
"Flashblock" extension and get the Eweek crash with that enabled anyway.

User agent is: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416
Fedora/1.0.3-2 Firefox/1.0.3

Comment 3

[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 4

[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.