EXCEPTION_ACCESS_VIOLATION in HotSpot Virtual Machine:

122 views
Skip to first unread message

Bruce Petro

unread,
Dec 1, 2009, 1:47:54 PM12/1/09
to Google Web Toolkit
I'm hitting the error shown below in my code in the following manner...
Working with a fairly complex object composed of several component objects - so quite a bit of memory probably...
a) Editing an object, saving the results, then without clearing the screen, request the another object via RPC with the intention of refilling the screen with the new fresh values for the new object.  When the RPC send attempts to happen, the browser (IE or hosted) vanishes. If I'm in hosted mode then Eclipse console contains the error and reference to a detailed error file. (attached).
b) Interesting!  If instead of requesting a new object to edit, I instead go to the menu and re-draw the screen from scratch - then no error occurs.  

Theories:
a) We're running out of memory and I need to up the memory (can that be done in IE browser running javascript?)
b) The UI and its "ties" to the data module object is getting totally confused by swapping the model out from under it.

The detail file included seems to be hinting at memory, but I may be reading it wrong. Any ideas from anyone out there?  If it is memory, how does one go about increasing memory in a running javascript application?


#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x420c87ea, pid=1552, tid=5616
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_18-b02 mixed mode)
# Problematic frame:
# C  [Dxtrans.dll+0x87ea]
#
# An error report file with more information is saved as hs_err_pid1552.log
#
# If you would like to submit a bug report, please visit:
#

hs_err_pid1552.log

Karthik Abram

unread,
Dec 1, 2009, 2:11:15 PM12/1/09
to google-we...@googlegroups.com
I had the same issue with GWT 2.0.0-rc1 and rc2 with JDK1.5 update 22.
I switched to JDK 1.6 and the problem went away. I only had this
happen in "development" mode, and consistently so.
> --
>
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-tool...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>

Bruce Petro

unread,
Dec 1, 2009, 2:19:06 PM12/1/09
to google-we...@googlegroups.com
Thanks!  I cannot switch java versions but I can work on memory issues in general.  

BTW: I was sloppy. I failed to mention I'm working in 1.6.4 version.  Also, if others are searching this in the future, I believe I should abandon the UI -> model links as an issue. The reason is the detail file indicates memory AND debugging, the crash consistently comes at the moment of the send to the RPC for the next object and I would presume RPC send cycles are a high-point in memory and resource usages.
Reply all
Reply to author
Forward
0 new messages