Closed Bug 289915 Opened 20 years ago Closed 19 years ago

crash on a plugin-heavy page

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: joni_mmm, Unassigned)

References

()

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; tr-TR; rv:1.7.6) Gecko/20050321 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; tr-TR; rv:1.7.6) Gecko/20050321 Firefox/1.0.2

In the page at http://www.yatirimyap.com, graph in stock details crashed. My
operating system is Win 2000 service pack 4. Each time i entered that site it
failed to open graphs. Because of that i have to use explorer...

Reproducible: Always

Steps to Reproduce:
1.open http://www.yatirimyap.com
2.choose below graph (Grafik) and stock (hisse) for the detailed graphically
information for times.
3.The page failed to open.

Actual Results:  
The bar below is open but the chart can not be displayed
Group: security
Keywords: crash
Summary: This is a stock market web site. In detailed information like chart, the browser crashed and failed to display it. → This is a stock market web site. In detailed information like chart, the browser crashed.
That's a very busy page, with java and flash applets. What are your plugin
versions? I can't reproduce a crash, but the page doesn't exactly work correctly
either. When I use the navigation frame at the bottom I get "page not found"
from the server. If I capture the URL and load it directly it loads fine for me.
Assignee: bugs → nobody
Severity: normal → critical
Component: JavaScript Console → General
QA Contact: javascript.console → general
Summary: This is a stock market web site. In detailed information like chart, the browser crashed. → crash on a plugin-heavy page
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.