Page 1 of 1

GrowlMenu taking HUGE amounts of Virtual Memory

Posted: Wed Oct 21, 2009 4:46 am
by MintCondition
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?

Re: GrowlMenu taking HUGE amounts of Virtual Memory

Posted: Wed Oct 21, 2009 5:18 am
by boredzo
Please run this command in Terminal:

Code: Select all

vmmap -w GrowlMenu > ~/"GrowlMenu-vmmap.txt"


That command will create a file named GrowlMenu-vmmap.txt in your Home folder. Please post it here using the “Upload Attachment” tab on the reply form.

Re: GrowlMenu taking HUGE amounts of Virtual Memory

Posted: Wed Oct 21, 2009 5:27 am
by MintCondition
Here you go. Looking at the file, the suspicious entry is "MALLOC [32.0G]"

Hope this helps!

Re: GrowlMenu taking HUGE amounts of Virtual Memory

Posted: Wed Oct 21, 2009 6:57 am
by boredzo
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.

I doubt that this is the performance problem you're looking for.

Re: GrowlMenu taking HUGE amounts of Virtual Memory

Posted: Wed Oct 21, 2009 1:14 pm
by MintCondition
The attached files were taken about 30 seconds apart. So yes, Activity Monitor shows it.

You may be right about the performance issues being unrelated, I'm starting to suspect an Hard Drive issue . :sad: