Skip to main content

How do you release "memory" when a workflow is completed?

Permanently deleted user
We have noticed that after running the same workflow or many workflows in a site, the memory usage keeps accumulating, acting  as if the workflow was not releasing memory upon completion.  This has been slowing down the site, the longer a user engaged and running workflows.  How can we release the memory a workflow uses during or after a session?

 

J
0

Comments

5 comments

Date Votes
  • Ryan Kelley
    I just submitted a critical ticket for this:

     

    Subject: GC 4.4 Memory leak?

     

    Description We have two instances of GeoCortex Essentials 4.4 installed. One instance is installed on a windows server 2008 R2, the other on a 2012 R2. windows server. Both are experiencing an increased load of physical memory. Running a workflow, a very simple one, will add almost 100MB of physical space onto the server. There is no GP service involved, just GC workflow activities. The memory never comes back down. The CPU is stable. This is not the case on the same workflows being run on a version of GC 4..2.2 or 4.3.0. This is critical that we have this fixed before we deploy to our dev and prod servers.
    0
  • Stefan Schweigert

    Hello Jeff and Ryan,

    You can use the Dispose activity to release unmanaged resources.

     

    We will likely need to take a look at these workflows in order to track down the issue as we have not been able to reproduce this issue.

    Thanks, Stefan

    0
  • Ryan Kelley
    We've started looking into that activity in workflow. But why all of a sudden would we need to use this? Also, is there an example of how to use this? Lastly, how do we know what constitutes as an unmanaged resource?
    0
  • Stefan Schweigert

    Hi Ryan,

     

    There's no reason why you would need to start using it if you hadn't already. It's useful when you are generating bitmap files within the workflow.

     

    There also hasn't been any changes to workflows that would explain why GE 4.4 is causing this issue. We will need to take a look at your workflow to track down the issue.

    Thanks, Stefan.

    0
  • Ryan Kelley
    Hi Stefan,

     

    I have someone calling me about this from Latitude this am. But yeah, the workflows I have tested are not downloading any images, just some simple Query Tasks, Get/Set Extents from featureSets returned. Pretty basic stuff. 
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post