I've been trying to trouble shoot some performance problems with my 3.06 24" iMac lately. When I started poking around in Activity Monitor, I noticed that growlMenu was taking about 16MB of Real Memory and 35 GIGABYTES of Virtual Memory.

This seems like a problem. Killing the process and relaunching it seems makes the VM jump right back to 35GB.

Umm... help?

Last edited by boredzo on Wed Oct 21, 2009 5:01 am, edited 1 time in total.
Reason:Correcting title, which previously said that Growl was using all this memory.

MintCondition wrote:Looking at the file, the suspicious entry is "MALLOC [32.0G]"

Did you confirm that Activity Monitor was showing 32+ GiB of VM for GrowlMenu at the time you took this sample? For me, Activity Monitor appears to ignore memory ascribed to malloc.

Also, it's worth noting that both your vmmap output and my vmmap output show practically nothing (exactly nothing, in my case) allocated in the “Writable Regions” section. This suggests that all that malloc memory either has already been freed or is potential memory that GrowlMenu could allocate if it wanted it.