Closed Bug 283758 Opened 20 years ago Closed 19 years ago

crash with segfault if I open this page with certain plugins installed

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: dkutcher, Assigned: bugzilla)

References

()

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050225 Firefox/1.0+
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2) Gecko/20050225 Firefox/1.0+

The page listed above causes FF to close without any notification or talkback. 
The page is usually part of a frameset.  You should be able to get it by
navigating to http://www.worldtribune.com and opening one of the news stories in
the middle of the page.  This nightly FF build reports a segfault on the command
line: ./run-mozilla.sh: line 131: 20483 Segmentation fault      (core dumped)
"$prog" ${1+"$@"}
There are no symbols in the executable so gdb wasn't much help.  I found this by
clicking a link on www.drudgereport.com .

Reproducible: Always

Steps to Reproduce:
1.navigate to url http://www.worldtribune.com/worldtribune/left.htm (part of
frameset but can be loaded separately as part of one of the news stories in the
main page)
2.
3.

Actual Results:  
Browser closed without notification or talkback.  The nightly build from 2/25
said it had a seg fault on the command line.  The 1.0 version that came with FC3
just closed without any message or talkback.

Expected Results:  
displayed page contents.

talkback doesn't display.
extensions installed and enabled: CookieCuller 1.1.0 and Flashblock 1.2.9.  If
either one is disabled the page loads fine.
This problem occurs only in Fedora Core 3 with these plugins enabled.  The page
loads fine on Windows XP with FF 1.0 preview release (Gecko/20041001).
The problem may go away if the site changes content.
I was only able to reproduce this problem if I navigated to the site.  If I
saved the page locally (Save Page As) it would load and display fine.
*** Bug 283762 has been marked as a duplicate of this bug. ***
Keywords: crash
the example url crashes my firefox v1.02 browser also--even running
in safe-mode.  

here is another link that does the same thing:

http://thinks.com/games

i built firefox on a very fresh gentoo 2005.0 installation- 
linux 2.6.11-r5- gcc-3.3.5- glibc-2.3.4.20041102-r1

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050324 Firefox/1.0.2

console message:

 /usr/libexec/mozilla-launcher: line 542: 12725 Segmentation fault     
"$mozbin" "$@"

firefox-bin exited with non-zero status (139)


don't see a coredump



i fixed my problem--i guess it was just a compiler issue.  people on gentoo forum
said official build does not have the segfault problems that some have with local
builds.  was going to try official build, but then saw gcc, bin86 and libtool 
had newer gentoo versions.  in changelogs i don't see any x86 relevant changes 
for gcc and bin86, but i see some in libtool.

retracting my vote.  sorry for not testing more first.
 
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.