On May 22, 2010, at 17:08:08, Gary L. Gray wrote:
> Using only Cocoa notifications seems to have cured the continuously
> increasing usage of RAM.
Well, no, it's a workaround. You're supposed to be able to use WebKit-based
displays without the RAM usage inflating.
Please do the following:
1. Switch Growl back to a WebKit-based display.
2. Kill GrowlHelperApp using the Activity Monitor. (*Don't* turn it off in the
prefpane.)
3. In a terminal window, run Growl with MallocStackLogging turned on:
MallocStackLogging=1
/L*/P*P*/Growl.prefPane/C*/R*/GrowlHelperApp.app/C*/M*/GrowlHelperApp
4. Make some notifications happen.
5. Once Growl's memory usage has crept up significantly, run leaks:
leaks GrowlHelperApp > GrowlHelperApp-leaks-$USER.txt
and heap:
heap GrowlHelperApp > GrowlHelperApp-heap-$USER.txt
6. Post the two files in the Files area:
http://groups.google.com/group/growldiscuss/files
7. Send us the links to the two files.
--
You received this message because you are subscribed to the Google Groups
"Growl Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en.
