[Neo] out of swap space
johan at neotechnology.com
Tue Jul 21 12:01:46 CEST 2009
Again you have run into a JVM bug
(http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6423256, and it
should have been marked as a bug not "request for enhancment").
I would suggest you update your JDK to the latest one (update 14) and
hopefully the problem will go away. If it does not try send in the
-Xms and set initial heap to max heap (such as java -Xms1024M
-Xmx1024M). Also if you are running in client mode try the -server
On Tue, Jul 21, 2009 at 10:36 AM, Symeon (Akis)
Papadopoulos<papadop at iti.gr> wrote:
> Hi all
> While processing a large Neo graph (in the order of 300k nodes - 2M
> edges), the Java Virtual Machine crashed with the following message:
> # An unexpected error has been detected by Java Runtime Environment:
> # java.lang.OutOfMemoryError: requested 1024000 bytes for GrET in
> Out of swap space?
> # Internal Error (allocation.inline.hpp:42), pid=308, tid=3572
> # Error: GrET in
> # Java VM: Java HotSpot(TM) Client VM (10.0-b19 mixed mode, sharing
> # An error report file with more information is saved as:
> # [location on my hard drive]\hs_err_pid308.log
> # If you would like to submit a bug report, please visit:
> # http://java.sun.com/webapps/bugreport/crash.jsp
> Most posts I've seen on the net regarding this issue suggest reducing
> the memory used by the JVM by means of a lower -Xmx value.
> Although I tried this (lowering from 1024m to 768m and then to 512m on a
> Windows machine with 2GB RAM), the JVM crash still occurred.
> Are you aware of any Neo-specific programming practices that would help
> avoid this crash?
> PS> The same problem was reported by a colleague of mine while
> processing a different graph of similar size on his Windows PC
> (equipped with more memory - 4GB).
> Best regards,
More information about the User