359736 - crash when entered any ASX Code (e.g. TLS) and then select "1 Year Chart"

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[nickvapt1]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

The actions described above are causing the browser to crash (it is not a kind of crash that is detected by windows) - the effect is the browser does not respond any more to clicking on links, etc. any more. Moreover the application window can be closed, but can not be restarted again as it is still running, but without a window. So, to recover from this situation there are 2 ways - either to restart windows, or to kill the firefox.exe from the task manager.

Reproducible: Always

Steps to Reproduce:
1. Select any 3 letter valid ASX code (e.g. TLS or WBC)
2. From the drop down box "summary" select "1 Year Chart:
3. Press the "Go!" button

Actual Results:  
Firefox is sort of frozen - does not respond to clicking on links, etc.
There is no actual crash detected by windows, so not sure how to collect details.

Expected Results:  
To display a graph - the result is only partially displayed and then goes frozen.

The above web page works fine with Internet Explorer 6.0.2900.2180.xpsp_sp2_gdr.050301-1519

Perhaps this web page is using some non-standard features implemented only by microsoft...

I really would like to assist with this bug, so please provide some ideas what else to collect

Comment 1

[Steve England [:stevee]]

Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!

Comment 2

[Steve England [:stevee]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.6pre) Gecko/20070724 BonEcho/2.0.0.6pre ID:2007072403

WFM and no response from reporter re: comment 1 -->WORKSFORME.
Reporter, if you still see this problem with the latest release of Firefox 2, please reopen this bug. Thanks!