Submitted On 12-JUN-2000
McLennanN
This bug also existed in all versions of JDK/JRE 1.2 on
Windows NT.
Submitted On 26-JUL-2000
peteC
I have found code running on Cyrix CPUs will encounter this
bug much more often than code running on other CPUs. I have
a Cyrix 6x86MX that is used for testing which fails quite
often because of this bug. However I have only begun after
I made the move to 1.3 on windows.
The poor quality of the Cyrix FPUs has been discussed in
newsgroups and forums across the net for some time so its
not surprising that they should trigger this bug.
Submitted On 16-AUG-2000
MichaelDawson
If this causes problems with your processor the only option
is to remove the code that throws the exception. Rem (//)
out the throw statement and add a System.out.println();
call in it's place. Then recompile and place in rt.jar.
There appear to be problems with serialization.
Submitted On 04-JAN-2001
TorreC
It looks like this bug is showing up using JRE 1.3 on a Power
Mac G4 running Virtual PC 4.0 (Windows 98).
Submitted On 03-FEB-2001
LeidelJ
This bug also exists on JDK 1.3 on
Windows 95 with Cyrix 6X86MX.
Submitted On 06-FEB-2001
adolos
This also occurs running JRE 1.3 under Windows 2000
on Virtual PC 4 on Macintosh.
Submitted On 12-FEB-2001
BerndPross
I encounter this Bug starting Forte on NT 4.0 with a cyric
Processor. Is there any work around to start Forte
propperly ?
Thanks for any hint.
Bernd
Submitted On 14-FEB-2001
TorreC
JRE 1.3.1 (beta) on my Mac G4 with Virtual PC 4.01 running
Windows 98: no longer throws the exception on the applet that
used to always crash with JRE 1.3.01. I did not see in the
release notes that this bug was addressed in that (beta)
release, but I am not complaining. I would be interested to
see if anyone else has a similar experience.
Submitted On 22-FEB-2001
ScottEllsworth
1.3.1 beta did not help this problem for me on my Powerbook
G4 with vpc. I have sent the issue to Connectix, but I do
not know what to do about it.
Any other suggestions?
Submitted On 11-MAR-2001
Hypnus
This bug occurs on my iMac G3 (384Mb RAM, 500Mhz)
with VPC 4.0 Win98 and Forte for Java 1.0 (CE). Using
the JDK 1.3.1 beta allows Forte to start up, but the
control pallet is not initialised and the menus do not
react.
Can anyone help?
Submitted On 16-SEP-2001
vy_ho
I have a Cyrix II 333 Mhz, and this problem crops up all
them time. I was searching desparately for a Cyrix fix.
However, they were sold to Via, and Via has one of the
worst customer support web site I've seen from a world
class company. I wonder if any of you know a fix any where
please let me know. Also, because my other application
runs fine with this processor (I think so), only Java does
not. I wonder if it has something to do with Sun's
implementation. (My email is: st946tbf@drexel.edu)
Submitted On 01-OCT-2001
matthew22
I am experiencing this problem, when running deploytool in
J2EE 1.3 with J2SE 1.3.1_01 on W2k(SP2). Is anybody in the
Sun doing about this something?
matthew@centrum.sk
Submitted On 01-OCT-2002
vy_ho
Same problem on the HashMap, my work around is around line
163 of jdk1.4.1, I put:
if ((loadFactor <= 0) || (loadFactor > 1)){
//throw new IllegalArgumentException("Illegal
load factor: " +
loadFactor);//
loadFactor = 0.75;
}
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
