Ticket #3560 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Memory leak with Load algorithm

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: major Milestone: Iteration 30
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Janik Zikovsky

Description (last modified by Martyn Gigg) (diff)

Running the Load algorithm and then deleting result workspace does not free up the memory used but if the specific algorithm is called by name then the memory is freed.

To reproduce:

  • Click the Load button and find a file
  • Open up some type of memory monitor and check the value
  • Select the workspace and click delete.
  • The memory is not released.

Perform the same steps with the sub-algorithm directly from the algorithm search box ,e.g. LoadRaw for a raw file, and the memory is retrieved after the delete.

This may or may not be related to #3407

Change History

comment:1 Changed 9 years ago by Martyn Gigg

  • Status changed from new to accepted

comment:2 Changed 9 years ago by Martyn Gigg

  • Description modified (diff)

comment:3 Changed 9 years ago by Martyn Gigg

  • Status changed from accepted to verify
  • Resolution set to fixed

In [13959]:

Fix a memory leak (well holding onto a shared_ptr too long) in the AlgorithmProxy after an algorithm has executed. Fixes #3560

comment:4 Changed 9 years ago by Janik Zikovsky

  • Status changed from verify to verifying
  • Tester set to Janik Zikovsky

comment:5 Changed 9 years ago by Janik Zikovsky

  • Status changed from verifying to closed

Confirmed, no leak after 20 runs.

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​4407

Note: See TracTickets for help on using tickets.