Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-14751

Huge memory usage DbEntityManager

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Cannot Reproduce
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • engine
    • None

      Environment (Required on creation):

      Camunda 7.14.0

      Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

       

      We got huge memory usage on our production and after the heap dump analyzing we got that most of memory is used by camunda and expecially by DbEntityManager class.

       

       

      Steps to reproduce (Required on creation):

      Run big number of process instances with full history level

      Observed Behavior (Required on creation):

      Huge memory usage

      Expected behavior (Required on creation):

       

      No memory leacks 

      Root Cause (Required on prioritization):

      See description 

      Solution Ideas (Optional):

       

      Store in cache only these objects camunda won't work without 

      Hints (optional):

        This is the controller panel for Smart Panels app

          1. image-2022-07-06-11-31-48-887.png
            image-2022-07-06-11-31-48-887.png
            120 kB

            [CAM-14751] Huge memory usage DbEntityManager

            Thorben Lindhauer added a comment -

            Hi,

            Please provide a proper analysis of the memory issue that you are observing. What is currently missing:

            • Numbers: What is the heap size you are running the application with? How does the heap size develop over time?
            • Analysis: Why do you think this is caused by Camunda? What code causes this?

            I'm sorry that we can't do memory analysis for you. If you can point us to a specific problem in our code, we are happy to fix it.

            Please note that the DbEntityManger and DbEntityCache objects only live for as long as an (API) command runs. Once a command completes, the entity manager and cache are dereferenced and garbage-collected. If however that command loads a lot of data (e.g. because it makes a query with many results), then you may see an increase in memory consumption while that command runs. Also, if the command never returns (e.g. in the case of an infinite loop in the process), then the memory will also not be freed up.

            Cheers,
            Thorben

            Thorben Lindhauer added a comment - Hi, Please provide a proper analysis of the memory issue that you are observing. What is currently missing: Numbers: What is the heap size you are running the application with? How does the heap size develop over time? Analysis: Why do you think this is caused by Camunda? What code causes this? I'm sorry that we can't do memory analysis for you. If you can point us to a specific problem in our code, we are happy to fix it. Please note that the DbEntityManger and DbEntityCache objects only live for as long as an (API) command runs. Once a command completes, the entity manager and cache are dereferenced and garbage-collected. If however that command loads a lot of data (e.g. because it makes a query with many results), then you may see an increase in memory consumption while that command runs. Also, if the command never returns (e.g. in the case of an infinite loop in the process), then the memory will also not be freed up. Cheers, Thorben

              Unassigned Unassigned
              a.pankratiev Alexander Pankratiev
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: