Ticket #2394 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

Memory leaks on running LoadTest

Reported by: Russell Taylor Owned by: Martyn Gigg
Priority: major Milestone: Iteration 28
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Russell Taylor

Description

Running the LoadTest under valgrind shows a significant amount of memory being leaked. This mostly appears to be in the main code rather than just the test. At least one of these is in the fileCheck method, which would not be good if it's going to be run every time a file is loaded.

Attachments

LoadLeaks.txt​ (50.5 KB) - added by Russell Taylor 10 years ago.
rhel5 valgrind output in revision 9459

Change History

comment:1 Changed 10 years ago by Nick Draper

  • Owner set to Martyn Gigg
  • Status changed from new to assigned

comment:2 Changed 10 years ago by Martyn Gigg

  • Status changed from assigned to accepted

comment:3 Changed 10 years ago by Martyn Gigg

(In [9447]) Fix some memory leaks. Others still lurking but appear to be in NeXus. Need to test on other machine. Re #2394

comment:4 Changed 10 years ago by Martyn Gigg

(In [9455]) Add more flexible simple API command for Load. Re #2330. Clean up for memory leak in LoadSNSNexus. Re #2394

Changed 10 years ago by Russell Taylor

rhel5 valgrind output in revision 9459

comment:5 Changed 10 years ago by Martyn Gigg

(In [9471]) Fix a test and implement LoadDialog python function. Refs #2330 and Refs #2394

comment:6 Changed 10 years ago by Russell Taylor

(In [9476]) Fix more memory leaks. Re #2394.

comment:7 Changed 10 years ago by Russell Taylor

The only ones left for me are from within the Nexus library.

comment:8 Changed 10 years ago by Russell Taylor

(In [9482]) Revert change that broke a test for some reason. Re #2394.

comment:9 Changed 10 years ago by Nick Draper

  • Milestone changed from Iteration 27 to Iteration 28

Bulk move of tickets at the end of iteration 27

comment:10 Changed 10 years ago by Martyn Gigg

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

Apart from those out of our control, they are gone.

comment:11 Changed 9 years ago by Russell Taylor

(In [11095]) Clear a couple of small memory leaks. Re #2394.

comment:12 Changed 9 years ago by Russell Taylor

  • Status changed from verify to verifying
  • Tester set to Russell Taylor

comment:13 Changed 9 years ago by Russell Taylor

  • Status changed from verifying to closed

Removed a couple more that had probably come along since this ticket was resolved. All clear again now.

comment:14 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​3241

Note: See TracTickets for help on using tickets.