Discovered an odd problem and wondering if it sounds familiar to anyone else… Legacy plugin built from a JUCE fork in the 4.0.1 era - runs fine on any OS 10.10 and below. Starting with OS 10.11 El Capitan, opening/closing the plugin UI (ie. clicking on the insert in Pro Tools) results in dramatic memory increases displayed in Activity Monitor - around 100Mb per open/close cycle which is probably close to the whole memory footprint of the plug. It’s not constant, though - it increases in size a bit with each cycle. Memory use is stable while the plug-in is either open or closed. Memory use is stable under previous OSes.
“Does it happen on the tip?” - This is a legacy plug and the massive changes from 4.0.1 to current tip make it impractical to migrate to the latest. Hoping this sounds familiar to someone and a fix can be cherry-picked. The El Cap headaches I see in the repo seem to be more focused on rect coalescing and repaint message queueing, which seems unlikely to be related.
Anyone else recall seeing anything like this?
Edited: OS versions were off by .1 in OP. Problems start in 10.11 El Cap, also confirmed in 10.12 Sierra.