Valgrind detects memory leaks

Description

Valgrind reports a variety of memory leaks introduced over time, along with a few mismatched new/delete calls.

Environment

None

Activity

Scott Cantor August 7, 2012 at 1:09 AM

log4cpp code has some issues with leaks whenever a new properties config is installed, but this is relatively rare in the SP code, and fixing it will be risky.

Scott Cantor August 2, 2012 at 5:10 PM

Plugged a few new leaks prior to release. Need to investigate some log4shib related messages that may be leaks inherited from log4cpp, setting as Blocker so I don't forget.

Scott Cantor September 20, 2011 at 8:03 PM

To avoid confusion: those experiencing large spikes in RAM usage (like multi gigabyte) are not going to solve anything plugging these small leaks.

You're using Apache in prefork mode, and you need to either stop (use worker mode) or reduce the default stack size using the stackSize option or a ulimit command.

Fixed

Details

Assignee

Reporter

Original estimate

Fix versions

Affects versions

Created September 12, 2011 at 3:47 PM
Updated August 7, 2012 at 1:11 AM
Resolved August 7, 2012 at 1:09 AM