Ticket #4182 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Run Mantid through memcheck and fix any issues

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: major Milestone: Release 2.0
Component: Mantid Keywords:
Cc: taylorrj@… Blocked By:
Blocking: Tester: Stuart Campbell

Description

There have been reports of Mantid using more memory than it used to. Lets start with this by checking what we can with valgrind's memcheck.

Note that this requires Mantid to be built without tcmalloc as that interferes with the checking.

Change History

comment:1 Changed 9 years ago by Martyn Gigg

Refs #4182. Cut memory from 27MB to 424 bytes during ConvertUnits test.

Memcheck showed up some fairly obvious memory leaks while running the ConvertUnits unit test. Fix these larger obvious ones first. More checks will be run as well

Changeset: fd80496bf9970d0d96892919a3117753740e34a2

comment:2 Changed 9 years ago by Martyn Gigg

Refs #4182. Another small, easy-to-fix leak found by memcheck.

Changeset: 888f7ba9112fe20e8b169af05e9ef96da72d720b

comment:3 Changed 9 years ago by Martyn Gigg

  • Status changed from new to accepted

comment:4 Changed 9 years ago by Martyn Gigg

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

comment:5 Changed 9 years ago by Stuart Campbell

  • Status changed from verify to verifying
  • Tester set to Stuart Campbell

comment:6 Changed 9 years ago by Stuart Campbell

  • Status changed from verifying to closed

Changes look reasonable.

comment:7 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​5029

Note: See TracTickets for help on using tickets.