Ticket #500 (closed: fixed)

Opened 12 years ago

Last modified 5 years ago

Investigate (and fix!) memory leakage issues

Reported by: Russell Taylor Owned by: Russell Taylor
Priority: minor Milestone: Iteration 16
Component: Keywords:
Cc: Blocked By:
Blocking: Tester:

Description

Run a script multiple times and the memory usage just keeps on growing. First issue to sort: Only hold a limited number of past algorithms (AlgorithmProxy) in the AlgorithmManager instead of all of them. Second issue: There's still a significant amount of memory being used up somewhere else. Don't know where yet.

Change History

comment:1 Changed 12 years ago by Russell Taylor

  • Status changed from new to assigned

comment:2 Changed 12 years ago by Russell Taylor

(In [2182]) Update AlgorithmManager to only keep a limited number of algorithms alive (default 100, config property name: algorithms.retained). This check-in will break qtiplot, which will be remedied shortly... Re #500.

comment:3 Changed 12 years ago by Russell Taylor

(In [2183]) Fixes to qtiplot for last change (even though it didn't realise it was broken). Re #500.

comment:4 Changed 12 years ago by Russell Taylor

(In [2213]) Add property. Re #500.

comment:5 Changed 12 years ago by Russell Taylor

  • Priority changed from critical to minor

The major problem here is sorted out by limiting number of old algorithmProxies stored. There are still memory leaks around though which should be sorted for their own sake and because they are probably contributing to the memory fragmentation slowdown that becomes apparent after a while.

comment:6 Changed 11 years ago by Russell Taylor

  • Status changed from assigned to closed
  • Resolution set to fixed

I'm sure there are still memory leaks in places, but for the moment they don't appear to be causing major problems.

comment:7 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​1348

Note: See TracTickets for help on using tickets.