Taverna 2

WorkflowInstanceFacade leaks memory per nested workflow run

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.1.0
  • Fix Version/s: 2.1.2
  • Component/s: Engine - General
  • Labels:
    None
  • Familiarity:
    Similar

Description

WorkflowInstanceFacade has a WeakHashMap from workflow ID to workflow instance. However, a WeakHashMap is only using weak references to the KEYs, ie. strings, and as the string for workflow ID is also inside the WorkflowInstanceFacadeImpl these entries would never be removed.

Should be changed to be a map to WeakReference<WorkflowInstanceFacade>. This public static map (..) is only used by net.sf.taverna.t2.activities.dependencyactivity.AbstractAsynchronousDependencyActivity as far as I can tell.

Activity

Hide
Stian Soiland-Reyes added a comment - 2010-02-01 16:07

use weak references to the facades to avoid facade memory leak.
don't add WorkflowRunIdentifier entity to context for nested workflows (not needed anyway - and also add a T2-1135 memory leak)

Show
Stian Soiland-Reyes added a comment - 2010-02-01 16:07 use weak references to the facades to avoid facade memory leak. don't add WorkflowRunIdentifier entity to context for nested workflows (not needed anyway - and also add a T2-1135 memory leak)

People

Vote (0)
Watch (0)

Dates

  • Created:
    2010-02-01 09:49
    Updated:
    2010-03-23 15:10
    Resolved:
    2010-02-01 16:07

Time Tracking

Estimated:
30m
Original Estimate - 30 minutes
Remaining:
30m
Remaining Estimate - 30 minutes
Logged:
Not Specified
Time Spent - Not Specified