I agree that the 8 GiB reservation is innocuous (if irritating). I will need to look at the Cocoa GC documentation to see if there is a way to reduce that initial reservation.
As for the > 30 GiB issue: I believe this to be separate. I am wondering whether it may actually not be a problem with Growl itself, but rather with the implementation of Cocoa, or perhaps with some interaction with another library. When I get a chance later this week I will run GrowlMenu under Instruments and see if I can reproduce the > 30 GiB issue. An interesting observation: Right now I see GrowlMenu showing in Activity Monitor with Virtual Mem = 215.0 MB. Looking at the detail pane, I see Virtual Memory Size: 10.68 GB, Virtual Private Memory: 215.0 GB. Clearly the top page of Activity Monitor shows Virtual Private Memory, even though the column is labeled Virtual Mem. I note, however, that when the Growl Menu VM usage shoots up, it is the Virtual Private Memory which increases... Spidey!!! -- 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.
