I created a web site where several pages have applets embedded. I'm running Windows2K here at home as my development platform. When I view the webpages with the applets on my own machine they load just fine. However, when I go to other computers that are running WindowsXP Pro, Internet Explorer begins to load the page with the applet then crashes. An error log gets placed on the Desktop by HotSpot that states an EXCEPTION_ACCESS_VIOLATION. I don't get it. Would someone please help. It is critical that I get a solution to this problem.
The full error log is below. The following line in the log is in reference to the class I built: 0x0fa66460 JavaThread "thread applet-mvcs.TableForm.class" [_thread_blocked, id=2572]
It says _thread_blocked, why? Why would the thread be blocked. Would that have anything to do with the fact that I was behind a firewall when trying to access the webpage?
# # An unexpected error has been detected by HotSpot Virtual Machine: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d0d1dda, pid=3884, tid=4064 # # Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode, sharing) # Problematic frame: # C [awt.dll+0xd1dda] #
--------------- T H R E A D ---------------
Current thread (0x04fc0170): JavaThread "AWT-Windows" daemon [_thread_in_native, id=4064]
Instructions: (pc=0x6d0d1dda) 0x6d0d1dca: c0 74 2e ff 74 24 04 e8 8a ea fe ff 59 6a 01 59 0x6d0d1dda: 89 88 fc 00 00 00 33 c0 39 4c 24 08 6a 00 0f 94
Stack: [0x0f370000,0x0f470000), sp=0x0f46f7ac, free space=1021k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [awt.dll+0xd1dda] C [USER32.dll+0x8734] C [USER32.dll+0x8816] C [USER32.dll+0xb4c0] C [USER32.dll+0xb50c] C [ntdll.dll+0xeae3] C [USER32.dll+0x9402]
Other Threads: 0x0216f310 VMThread [id=1240] 0x0003e828 WatcherThread [id=3496]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap def new generation total 576K, used 545K [0x20a70000, 0x20b10000, 0x211d0000) eden space 512K, 93% used [0x20a70000, 0x20ae8480, 0x20af0000) from space 64K, 100% used [0x20af0000, 0x20b00000, 0x20b00000) to space 64K, 0% used [0x20b00000, 0x20b00000, 0x20b10000) tenured generation total 1408K, used 678K [0x211d0000, 0x21330000, 0x26a70000) the space 1408K, 48% used [0x211d0000, 0x21279bf0, 0x21279c00, 0x21330000) compacting perm gen total 8192K, used 1224K [0x26a70000, 0x27270000, 0x2aa70000) the space 8192K, 14% used [0x26a70000, 0x26ba2380, 0x26ba2400, 0x27270000) ro space 8192K, 63% used [0x2aa70000, 0x2af7b178, 0x2af7b200, 0x2b270000) rw space 12288K, 46% used [0x2b270000, 0x2b809fa8, 0x2b80a000, 0x2be70000)
Environment Variables: PATH=C:\PROGRA~1\Java\JRE15~1.0_0\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;. USERNAME=Success College OS=Windows_NT PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 1, GenuineIntel
Alan, can we get more information about which jdk you are using to develop your applet? i would suggest trying to run your applet with jres older than 1.5.0_06 (it might have flaws you know, i had problems with this particular jre myself) that's one thing, another thing you might consider is to try to build a very simple applet (maybe some code is causing the crash, but really that is unlikely) for example that only displays some output statement, isolating the classes is a good idea always so that you know what is the real cause of crash, is it compatibility issue ... Maybe it's a display issue, since if i noticed correctly, it involves AWT... This is what i can think of at the moment... Best, Mohammad
Joined: Sep 24, 2003
Here's an update. I tried loading the webpage in three other seperate locations, one at Futureshop, second at the Sony store, and third at our local Xerox business where my wife works. In all three locations they have the latest jre and the applet loaded just fine. I have a sneeky suspician that this has something more to do with firewalls. Do you think that is a valid assumption? Do you know of any incompatibility issues or bugs with WindowsXP Pro regarding this issue?
[ April 12, 2006: Message edited by: Alan Shiers ] [ April 12, 2006: Message edited by: Alan Shiers ]