cocoaforge

At startup time GrowlHelperApp take ~5 MB of data and it shoots up to 65 MB in some time. is it memory leak or is it expected ?
For now I am just restarting it periodically. I am using latest OSX, on PPC

Sounds like a memory leak, certainly. The output of leaks GrowlHelperApp (typed at the terminal) might be helpful.

Which display are you using?

I attach an extra display but notifications are targeted on my primary laptop display.
At the time of this post it has grown to 28MB with 5 threads & 160 ports(??), CPU time-06.86 from Activity Monitor.


here is leaks output -

Process 3096: 17622 nodes malloced for 13572 KB
Process 3096: 46 leaks for 2368 total leaked bytes.
Leak: 0x003a28a0 size=96 instance of 'NSCFDictionary'
0x003016b0 0x00010394 0x00000002 0x00000002 .0..............
0x00000005 0xa1b1c1d3 0x00000000 0x00000000 ................
0x00000000 0x003a28cc 0x003a28e0 0x00339620 .........3.
0xa1b1c1d3 0x0031f0a0 0xa1b1c1d3 0xa1b1c1d3 .....1..........
0x003a0850 0x00000000 0x0039e9b0 0x00000000 .:.P.....9......
0x0003869b 0x0039f250 0x003a41b0 0x00000006 .....9.P.:A.....
Leak: 0x003a0f70 size=96 instance of 'NSCFDictionary'
0x003016b0 0x00010394 0x00000002 0x00000002 .0..............
0x00000005 0xa1b1c1d3 0x00000000 0x00000000 ................
0x00000000 0x003a0f9c 0x003a0fb0 0x003225f0 .....:...:...2%.
0xa1b1c1d3 0x0035a0c0 0xa1b1c1d3 0xa1b1c1d3 .....5..........
0x0030fe60 0x00323490 0x0030dab0 0x003a1fe0 .0.`.24..0...:..
0x0039f250 0x00000000 0x00000000 0x00000006 .9.P............
Leak: 0x003c4e40 size=96 instance of 'NSCFDictionary'
0x003016b0 0x00010394 0x00000002 0x00000002 .0..............
0x00000005 0xa1b1c1d3 0x00000000 0x00000000 ................
0x00000000 0x003c4e6c 0x003c4e80 0x003c5250 .....<Nl.<N..<RP
0xa1b1c1d3 0x003c4da0 0xa1b1c1d3 0xa1b1c1d3 .....<M.........
0x003c4dc0 0x003c79a0 0x003c4e10 0x0000000f .<M..<y..<N.....
0x00000000 0x00000000 0x003a5010 0x00010006 ..............
Leak: 0x003bf070 size=96 instance of 'NSCFDictionary'
0x003016b0 0x00010394 0x00000002 0x00000002 .0..............
0x00000005 0xa1b1c1d3 0x00000000 0x00000000 ................
0x00000000 0x003bf09c 0x003bf0b0 0x0035af70 .....;...;...5.p
0xa1b1c1d3 0x003befd0 0xa1b1c1d3 0xa1b1c1d3 .....;..........
0x003beff0 0x903cdb80 0x003bf040 0x00000000 .;...<...;.@....
0x903df9cc 0x00000001 0x003bb850 0x01902e00 .=.......;.P....
Leak: 0x003be700 size=96 instance of 'NSCFDictionary'
0x003016b0 0x00010394 0x00000002 0x00000002 .0..............
0x00000005 0xa1b1c1d3 0x00000000 0x00000000 ................
0x00000000 0x003be72c 0x003be740 0x003bb650 .....;.,.;.@.;.P
0xa1b1c1d3 0x003bb6c0 0xa1b1c1d3 0xa1b1c1d3 .....;..........
0x003bb6a0 0x00000000 0x003be6d0 0x003a4750 .;.......;...:GP
0x0000357b 0xa07c1964 0x0030f790 0xa07c195c ..5{.|.d.0...|.\
Leak: 0x003be010 size=96 instance of 'NSCFDictionary'
0x003016b0 0x00010394 0x00000002 0x00000002 .0..............
0x00000005 0xa1b1c1d3 0x00000000 0x00000000 ................
0x00000000 0x003be03c 0x003be050 0x003bb8e0 .....;.<.;.P.;..
0xa1b1c1d3 0x003be120 0xa1b1c1d3 0xa1b1c1d3 .....;. ........
0x003be140 0x00323930 0x003be190 0x003be070 .;.@.290.;...;.p
0x00000000 0x00000000 0x00000000 0x00000000 ................
Leak: 0x003bd550 size=96 instance of 'NSCFDictionary'
0x003016b0 0x00010394 0x00000002 0x00000002 .0..............
0x00000005 0xa1b1c1d3 0x00000000 0x00000000 ................
0x00000000 0x003bd57c 0x003bd590 0x003b9c20 .....;.|.;...;.
0xa1b1c1d3 0x003b9c70 0xa1b1c1d3 0xa1b1c1d3 .....;.p........
0x003b9c90 0x00000000 0x003bd520 0x00000008 .;.......;. ....
0x36585548 0x564bfbfb 0x36000000 0x00040000 6XUHVK..6.......
Leak: 0x003bb590 size=96 instance of 'NSCFDictionary'
0x003016b0 0x00010394 0x00000002 0x00000002 .0..............
0x00000005 0xa1b1c1d3 0x00000000 0x00000000 ................
0x00000000 0x003bb5bc 0x003bb5d0 0x003ba930 .....;...;...;.0

-- truncated

By display if you meant display style then its Bubbles. Network notifications are not enabled. I have 0.7.4 version.

Well, the problem is not actually a memory leak in the progamming sense of the word -- basically all memory is accounted for. That doesn't mean that there isn't a memory useage growth problem. A lot of work has been done towards Growl 0.80; I wouldn't be surprised if this problem is already fixed. Next time I run 0.80 I'll take a look at its useage over time.