[Bug 1160] OpenJDK Bug with huge count of memmory and huge pages

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1160

Xerxes Rånby <xerxes at zafena.se> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
          Component|JamVM                       |IcedTea
         Resolution|---                         |INVALID
           Assignee|xerxes at zafena.se            |gnu.andrew at redhat.com
           Severity|blocker                     |normal

--- Comment #1 from Xerxes Rånby <xerxes at zafena.se> ---
The only thing that you can read out from the log file is that all if your
memory heap is full,

most likely caused by
a) a memory leak in the minecraft server software.
try monitor the jvm over time using VisualVM or Termostat, you may spot memory
leaks if the garbage collector runs are unable to return the heap to a constant
level.
http://java.dzone.com/news/how-fix-memory-leaks-java

b) to little available ram to host these giant datastructures.
have you tested all suggestions found in the log?

# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 217088 bytes for offset
table expansion
# Possible reasons:
#   The system is out of physical RAM or swap space
#   In 32 bit mode, the process size limit was hit
# Possible solutions:
#   Reduce memory load on the system
#   Increase physical memory or swap space
#   Check if swap backing store is full
#   Use 64 bit Java on a 64 bit OS
#   Decrease Java heap size (-Xmx/-Xms)
#   Decrease number of Java threads
#   Decrease Java thread stack sizes (-Xss)
#   Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
#  Out of Memory Error (blockOffsetTable.cpp:79), pid=675, tid=140598200018688


c) You may want to try running your application with different garbage
collectors, some may be faster to clear up the heap of old objects.


If you still think that it is a bug in IcedTea then you need to attach a
reproducer that can reproduce the issue on one of the IcedTea developers
machine. Preferably a standalone testcase.

For paid support try first contact the bukkit server team directly, they can
then better analyse your application + datastructure and look for memory leaks
in the bukkit server code.
You may also try contact any freelancer or company who can help you analyze
your issue.



All in all there is nothing in your report that indicate a bug in the IcedTea
or OpenJDK JVM itself. Therefore i will close this bug as INVALID unless you
can provide a testcase that clearly demonstrate that this out of memory is a
bug in icedtea.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20120907/0baea9b2/attachment.html