294039 - crash when I look at this page

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Gjalt Loots]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Crash.

Reproducible: Always

Steps to Reproduce:
1. Load page
Actual Results:  
Error window, stating memory reference. Program closed.

Expected Results:  
Normal page display.

Comment 1

[Steve England [:stevee]]

WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050509
Firefox/1.0.4
WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050512
Firefox/1.0+ ID:2005051215

Reporter, can you try in firefox's safemode, or with a new profile, and report
back as to what happens? Thanks!

Also, does Talkback appear and have you submitted the bug to the mozilla
crash-tracking server? If so, please post the TalkbackID(s) of your crash.

Comment 2

[Gjalt Loots]

(In reply to comment #1)
> WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050509
> Firefox/1.0.4
> WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050512
> Firefox/1.0+ ID:2005051215
> 
> Reporter, can you try in firefox's safemode, or with a new profile, and report
> back as to what happens? Thanks!
> 
> Also, does Talkback appear and have you submitted the bug to the mozilla
> crash-tracking server? If so, please post the TalkbackID(s) of your crash.


Talkback doesn't appear; in safe mode firefox doesn't crash however keeps
loading the page forever.

Only extension I run, is adblock by the way (which is disabled in safe mode).

Comment 3

[Carsten Book [:Tomcat]]

WFM Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050513
Firefox/1.0+ with flashblock.

Comment 4

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

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