Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-20750

Slow Memory Leak in JSF tools

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 4.3.1.Beta1
    • 4.3.0.CR1
    • jsf
    • None

    Description

      Opening then closing jsf projects slowly consumes heap memory, whish leads to slowing down overal performance and eventually to GC overhead limit exceeded exceptions.
      Attached screenshot list:
      1. GC overhead limit exceeded error oom1.png;
      2. Heap Memory Usage timeline mem-usage.png;
      3. Heap Memory Objects filtered for "org.jboss.tools" heap-snapshot2.png;
      4. Heap Memory Objects none filtered heap-snapshot1.png;
      5. OOM Dialog oom2.pngж
      6. .log

      Attachments

        1. .log
          427 kB
        2. heap-snapshot1.png
          heap-snapshot1.png
          273 kB
        3. heap-snapshot2.png
          heap-snapshot2.png
          309 kB
        4. mem-usage.png
          mem-usage.png
          268 kB
        5. oom1.png
          oom1.png
          14 kB
        6. oom2.png
          oom2.png
          28 kB

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-21221 Slow Memory Leak in JSF tools

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is incorporated by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. JBDS-2948 Improve Performance of small and large projects

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. JBDS-2948 Improve Performance of small and large projects

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              scabanovich Viacheslav Kabanovich (Inactive)
              nivologd@gmail.com Denis Golovin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: