255307 - Crashes 50% when loading Real-Time Java thing.

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Ray]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040714
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040714

About 50% of the time, when i load the a "Real Time Stats" java thing from the
site, the java thing will flicker while its loading (it does that every time) ,a
nd then like i said 50% of the time it will crash all of Mozilla. This is the
onyl java thing that does it, there are other java things like
http://www.sportsline.com/mlb/scoreboard which work fine, and they appaer to be
similar. 

Reproducible: Sometimes
Steps to Reproduce:
1.Sadly you have to be a member to goto that site, but if by chance you are. The
Fantasy Baseball Site, and Draft and Trade, and then Real Time Stats.
2.
3.

Actual Results:  
Sometimes it works, sometimes it crashes.

Expected Results:  
.. Worked.

Don't remember, when it happens again, i'll write it down and add it on to this.

Comment 1

[Gérard Talbot]

Which version of JRE are you using? The latest available version of JRE is
1.4.2_05 downloadable at:
http://plugindoc.mozdev.org/windows.html#Java
Have you contacted [e-mail] to report this technical problem?
http://fantasy.sportingnews.com/baseball/faq/#70
What exactly makes you think that this is a Mozilla problem and not a java
applet issue?
Have you tried with other browsers like Netscape 7.1, Opera 7.x?
Is there a way to become a member without having to pay any fees... so that
someone can examine, verify the page and code if it becomes *established*,
certain that this is a Mozilla browser problem and not a java applet coding issue?

Comment 2

[Ray]

(In reply to comment #1)
> Which version of JRE are you using? The latest available version of JRE is
> 1.4.2_05 downloadable at:
> http://plugindoc.mozdev.org/windows.html#Java
> Have you contacted [e-mail] to report this technical problem?
> http://fantasy.sportingnews.com/baseball/faq/#70
> What exactly makes you think that this is a Mozilla problem and not a java
> applet issue?
> Have you tried with other browsers like Netscape 7.1, Opera 7.x?
> Is there a way to become a member without having to pay any fees... so that
> someone can examine, verify the page and code if it becomes *established*,
> certain that this is a Mozilla browser problem and not a java applet coding issue?
> 
> 
Only have the problem with Mozilla, thats why i posted it, Works fine with
Internet Explorer. And i have the most recent Java.

Comment 3

[Adam Hauner]

Ray: Could you provide TalkBack incident ID of your crash?

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.