Growl memory leakage...

The Growl forums have moved to Google Groups, this forum is read only.
pcm
Harmless
Posts: 1
Joined: Sat May 17, 2008 6:45 pm

Growl memory leakage...

Postby pcm » Sat May 17, 2008 7:11 pm

Hi!
I'm very satisfied (good idea, good software thanks) to use Growl on Mac OS X 10.4.11(Build 8S165) (ibook G4 PPC), but it seems it has some memory leakage unfortunately. :[
I usually never stop(shutdown) my mac, just close the lid (suspend to ram, no logout) except important software update which require rebooting.
So my uptime usually 20-30 days (depends on software updates), in that way the growl also running lots of days.
I realised that after a reboot in the task manager/monitoring the GrowlHelperApp run and consume about 7-15MB of RAM which is OK.
And couple of days after the memory usage increase up to 300!!MB however(a mounth of continuous running). :[
I never get any crash yet about this, but I think is not OK to consume that amount of RAM even if couple of days running...
I know if I restart Growl the problem is disappear, but this way I just trigger the next occurrence...
What about You think about this bug?
Bye Mark

User avatar
bgannin
Growl Team
Posts: 1817
Joined: Thu Dec 02, 2004 8:11 am
Location: ..here
Contact:

Re: Growl memory leakage...

Postby bgannin » Sat May 17, 2008 8:01 pm

What display are you using? It sounds like a WebKit based one that had memory usage issues that have been addressed for 1.1.3.
Try my software!

#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?

User avatar
Robby
Cocoaforge Admin
Posts: 2604
Joined: Mon May 01, 2006 3:00 am

Re: Growl memory leakage...

Postby Robby » Thu Jun 05, 2008 9:56 pm

I'm see some memory leakage, too on my Mac Mini G4 with OS X 10.4.11.
The style I'm using is Smokestack.

User avatar
boredzo
Cocoaforge Admin
Posts: 796
Joined: Mon Dec 06, 2004 7:49 am
Contact:

Re: Growl memory leakage...

Postby boredzo » Tue Jun 10, 2008 7:01 pm

Robby wrote:I'm see some memory leakage, too ….
The style I'm using is Smokestack.


Please run `leaks GrowlHelperApp` and `heap GrowlHelperApp` in your Terminal. Make sure you scrub the output in your text editor—there may be some info in there (especially if it went through a Growl notification) that you don't want to leave your machine. Then, please send it to us.

User avatar
The_Tick
Cocoaforge Admin
Posts: 4642
Joined: Thu Dec 02, 2004 6:06 am
Contact:

Re: Growl memory leakage...

Postby The_Tick » Wed Jun 11, 2008 2:45 pm

Please make sure you are on 1.1.3 as well

User avatar
Robby
Cocoaforge Admin
Posts: 2604
Joined: Mon May 01, 2006 3:00 am

Re: Growl memory leakage...

Postby Robby » Wed Jun 11, 2008 5:25 pm

I've been running 1.1.3 for a few days now and I haven't seen Growl eating memory since! :)

User avatar
The_Tick
Cocoaforge Admin
Posts: 4642
Joined: Thu Dec 02, 2004 6:06 am
Contact:

Re: Growl memory leakage...

Postby The_Tick » Wed Jun 11, 2008 7:21 pm

The webkit fixes had a lot to do with that. :)

User avatar
Robby
Cocoaforge Admin
Posts: 2604
Joined: Mon May 01, 2006 3:00 am

Re: Growl memory leakage...

Postby Robby » Wed Jun 11, 2008 8:30 pm

I guessed that was it! =-)


Return to “Growl”

Who is online

Users browsing this forum: No registered users