Opened 3 years ago

Last modified 21 months ago

#2200 assigned defect

ClearState of IStatefulItems is not always executed

Reported by: mkommend Owned by: swagner
Priority: high Milestone: HeuristicLab 4.0
Component: Optimization Version: 3.3.9
Keywords: Cc:

Description (last modified by abeham)

If an algorithm is paused and then prepared the ClearState method of IStatefulItems is not executed. The algorithm never reaches the stopped state in which ClearState is called. As a result all ThreadLocal objects of LookupParameters (cachesActualValues, executionContexts) and Operators (executionContexts) are not disposed correctly, which could result in a memory leak.

Change History (6)

comment:1 Changed 3 years ago by abeham

  • Description modified (diff)

comment:2 Changed 3 years ago by abeham

  • Milestone changed from HeuristicLab 3.3.10 to HeuristicLab 3.3.11

comment:3 Changed 3 years ago by gkronber

  • Owner changed from architects to swagner
  • Status changed from new to assigned

comment:4 Changed 2 years ago by ascheibe

  • Milestone changed from HeuristicLab 3.3.11 to HeuristicLab 3.3.12

comment:5 Changed 2 years ago by ascheibe

  • Milestone changed from HeuristicLab 3.3.12 to HeuristicLab 3.3.13

comment:6 Changed 21 months ago by ascheibe

  • Milestone changed from HeuristicLab 3.3.13 to HeuristicLab 4.0
Note: See TracTickets for help on using tickets.