[jdom-interest] SIGSEGV (segmentation fault) error occurred during init a JDOM element

Krishnendu Roy Chowdhury kroy9532 at yahoo.com
Mon Feb 25 19:57:21 PST 2013

Hi Rolf,

Thank you for your quick update. Initially I also thought that It's related to perm gen space related error. But in the logs I didn't find “java.lang.OutOfMemoryError: PermGen space” error and Problematic frame was J (Crash in Compiled Code) in the logs.  

Is the problem is related to JVM or have memory restrictions to reserve more memory to perm gen?


--- On Tue, 2/26/13, Rolf Lear <jdom at tuis.net> wrote:

From: Rolf Lear <jdom at tuis.net>
Subject: Re: [jdom-interest] SIGSEGV (segmentation fault) error occurred during init a JDOM element
To: "Krishnendu Roy Chowdhury" <kroy9532 at yahoo.com>
Cc: "JDOM Group" <jdom-interest at jdom.org>
Date: Tuesday, February 26, 2013, 6:55 AM


    Hi Krish.


      This problem is almost certainly not related directly to JDOM.
      PermGen space is typically very small, and only used for two
      common purposes:

       - storing class definitions

       - storing String constants


       For your interest, the most common causes of PermGen Exhaustion
      that I know of are:


      - using Tomcat and loading/unloading servlets - each 'classloader'
      has it's own space in PermGen, and since each servlet has it's own
      classloader the PermGen fills up fast because so many classes are
      duplicated in different places in PermGen

      - Using lots of String.intern() calls - String.intern() uses a
      String constant reference from PermGen (or creates one if there
      was not one already). If you have many calls to String.intern() it
      can fill up PermGen very fast. JDOM does not do String.intern()




      On 25/02/2013 1:30 AM, Krishnendu Roy Chowdhury wrote:



                    I have faced a problem related to segmentation fault
                    in Linux box. I got following error -



                    J org.jdom.Element.<init>(Ljava/lang/String;)V


                    siginfo:si_signo=SIGSEGV: si_errno=0, si_code=2
                    (SEGV_ACCERR), si_addr=0x00002aab2ac30000
                     occurred during error reporting (printing native
                    stack), id 0xb




                    It is also shows in the log that 100% use of PermGen
                    space. Why this segmentation fault occurred? Is it
                    related to JDK or JDOM?


                    In my understanding, problem is related to JDK and
                    occurred due to 100% use of PermGen space. But I am
                    not sure as Problematic frame is J. 


                    Another interesting point is "error occurred during
                    error reporting (printing native stack), id 0xb".


                    I am using JDK6up20 and Linux environment. Please
                    find attached logs for details.
                    help me. 




To control your jdom-interest membership:


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.jdom.org/pipermail/jdom-interest/attachments/20130225/86cf2f2c/attachment.html>

More information about the jdom-interest mailing list