Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15491

OOM in Jenkins after 1 day

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Jenkins 1.478 - Aix 5.3 - IBM Java 6

      Jenkins is out of memory after 1 day of use.
      I've analysed heapdump with IBM Support Assistant. The results are attached.

      Is it normal that these objects take so much space in the heap (see IBM-SupportAssitant-leak-analyse.PNG) ?

      Furthermore, I noticed that the number of loaded classes is continuously increasing (see loaded-classes.PNG). Is this normal? or is it related to the monitoring plugin which can not properly handle information of IBM JVM?
      It seems that this is related to it because the application crashes when the monitoring graph displays 50k loaded classes.

      How can I find the source of the problem?

      Thanks in advance,
      Michaƫl Pailloncy

        1. IBM-SupportAssitant-leak-analyse.PNG
          41 kB
          Michael Pailloncy
        2. IBM-SupportAssitant-leak-analyse-ApplicationShutdownHooks.PNG
          90 kB
          Michael Pailloncy
        3. IBM-SupportAssitant-leak-analyse-duplicated-classes.PNG
          100 kB
          Michael Pailloncy
        4. IBM-SupportAssitant-leak-analyse-histogram.PNG
          102 kB
          Michael Pailloncy
        5. IBM-SupportAssitant-leak-analyse-Introspector.PNG
          91 kB
          Michael Pailloncy
        6. IBM-SupportAssitant-leak-analyse-top-consumers.PNG
          44 kB
          Michael Pailloncy
        7. IBM-SupportAssitant-leak-analyse-top-consumers-classes.PNG
          57 kB
          Michael Pailloncy
        8. IBM-SupportAssitant-leak-analyse-WinstoneSession.PNG
          113 kB
          Michael Pailloncy
        9. loaded-classes.PNG
          37 kB
          Michael Pailloncy

            Unassigned Unassigned
            mpapo Michael Pailloncy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: