Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-4736

java_version fact creates heap dumps

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • None
    • java
    • None
    • Needs Assessment

    Description

      java_version fact collection sets heap size too low for some version, which causes fact java to crash and create a heap file:

      1. ls /root/hs_err_pid*|wc -l
        2828
      1. java -Xmx8m -version 2>&1
        #
      2. A fatal error has been detected by the Java Runtime Environment:
        #
      3. SIGSEGV (0xb) at pc=0x00007fdf05fd3377, pid=13401, tid=140595883497216
        #
      4. JRE version: 6.0_41-b41
      5. Java VM: OpenJDK 64-Bit Server VM (23.41-b41 mixed mode linux-amd64 compressed oops)
      6. Derivative: IcedTea6 1.13.13
      7. Distribution: Red Hat Enterprise Linux Server release 6.8 (Santiago), package rhel-1.13.13.1.el6_8-x86_64
      8. Problematic frame:
      9. V [libjvm.so+0x395377] __printf_chk+0x395377
        #
      10. Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
        #
      11. An error report file with more information is saved as:
      12. /root/hs_err_pid13401.log
        #
      13. If you would like to submit a bug report, please include
      14. instructions how to reproduce the bug and visit:
      15. http://icedtea.classpath.org/bugzilla
        #
        Aborted
      1. java -version 2>&1
        java version "1.6.0_41"
        OpenJDK Runtime Environment (IcedTea6 1.13.13) (rhel-1.13.13.1.el6_8-x86_64)
        OpenJDK 64-Bit Server VM (build 23.41-b41, mixed mode)
      1. cat /etc/redhat-release
        Red Hat Enterprise Linux Server release 6.9 (Santiago)

      Attachments

        Activity

          People

            Unassigned Unassigned
            vchepkov Vadym Chepkov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support