291061 - usually crash when accessing acronym finder page from dictionary.com page

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Kim McCall]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Just updated to 1.0.3 in Linux (via yum).
Firefox crashes after I click on the link to the URL above.
Seems to happen 9 of 10 times, but once didn't crash.
Note: I'm running Fedora Core 3 for i386 on an AMD x64 box.


Reproducible: Sometimes

Steps to Reproduce:
1. type unto address bar: "dict tam" (this takes you to
http://dictionary.reference.com/search?q=tam)
2. scroll down half way, until you see "TAM: in Acronym Finder"
3. click on the "TAM" link

Actual Results:  
Kablammo!  Firefox disappears.
If I invoke it from the command line, I get
  /usr/lib/firefox-1.0.3/run-mozilla.sh: line 159:  6139 Segmentation fault    
 "$prog" ${1+"$@"}


Expected Results:  
Should have gone to a page showing me the various things TAM might stand for,
namely http://www.acronymfinder.com/default.asp?p=dict&String=exact&Acronym=TAM

I'm running Fedora Core 3 for i386 on an AMD x64 box.

Terminal output:
 /usr/lib/firefox-1.0.3/run-mozilla.sh: line 159:  6139 Segmentation fault     
"$prog" ${1+"$@"}

Comment 1

[Kim McCall]

I was able (once) to access the page by entering its URL directly into the
address bar.  Then I clicked the "Reload current page" button, and firefox crashed.

Comment 2

[Kim McCall]

Using the Cookie Manager, I "Block"ed the use of cookies by
  www.acronymfinder.com
and, lo and behold, no more crashing!

I was able to access the specified URL, reload it several times.

Don't really know what this means, but it seems like a good clue.

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.