Ticket #8167 (closed: fixed)

Opened 7 years ago

Last modified 5 years ago

Memory leak in RemoteJobManager

Reported by: Russell Taylor Owned by: Russell Taylor
Priority: minor Milestone: Release 3.0
Component: Framework Keywords:
Cc: Blocked By:
Blocking: Tester: Peter Peterson

Description

Running the ConfigService unit test through valgrind highlights a memory leak in the XML parsing done by the RemoteJobManager class.

Change History

comment:1 Changed 7 years ago by Russell Taylor

  • Status changed from new to inprogress

Re #8167. Fix a memory leak.

Make sure the resources allocated by the Poco XML parsing are released. This is achieved by making sure release() is called on the object returned by getElementsByTagName(). Poco::AutoPtr does this on its destruction.

Changeset: 1e1cf4f51470e56bf0ae7d36ffacfe0dfbad38e5

comment:2 Changed 7 years ago by Russell Taylor

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

Running valgrind on the ConfigServiceTest (N.B. must have tcmalloc turned off) shows that there is now zero memory leaked.

comment:3 Changed 7 years ago by Peter Peterson

  • Status changed from verify to verifying
  • Tester set to Peter Peterson

comment:4 Changed 7 years ago by Peter Peterson

  • Status changed from verifying to closed

Merge remote branch 'origin/feature/8167_remotejobmanager_memory_leak'

Full changeset: ​ad7c760723121f70d4386dda23bd807a48144392

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​9012

Note: See TracTickets for help on using tickets.