Ya, that's always the question isn't it. And usually on a thread like this I'd start asking for more details, but since HWG is entirely redone none of it would help. Restarting the application isn't completely awesome, but at least there's a workaround.
On Wed, Oct 10, 2012 at 8:10 AM, Joel Waxman <[email protected]> wrote: > On 10/10/12 8:55 AM, Christopher Forsythe wrote: > > There are a few on the beta list seeing higher, so I want to see what we > can do about that. Otherwise HWG 2 would already have been submitted to the > store. > > On Wed, Oct 10, 2012 at 7:52 AM, Joel Waxman <[email protected]> wrote: > >> On 10/10/12 6:55 AM, Fabrizio La Rosa wrote: >> >> I noticed a big problem with HardwareGrowler on my iMac and my MacBook >> Pro; both are running Mac OS X 10.8.2, Growl 2.0 and HardwareGrowler 1.3.2. >> The *real* memory usage of HardwareGrowler was 400 Mb on the iMac and >> 270 Mb on the MBP, it dropped down to 25 Mb after I have simply quitted & >> relaunched it. >> I keep the iMac always on because I use it at work and I shutdown or >> reboot the MBP very seldom, I mostly put it in standby mode. >> I see that there are other reports about this issue dating back to almost >> one year ago, so I think that it should be fixed ASAP because it stops me >> from using this app that would be otherwise very useful. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Growl Discuss" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/growldiscuss/-/rS0uEf47FqMJ. >> 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. >> >> The most I have seen so far is 52.7 mb >> -- >> 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. >> > > > > -- > Chris Forsythe > @The_Tick <http://twitter.com/The_Tick> > > -- > 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. > > Here is what I see with both entries.: > 966 com.growl.HardwareGrowler.GNTPClientService joel 0.0 2 > 26.0 MB Intel (64 bit) 92 0.19 > 571 HardwareGrowler joel 0.0 2 54.0 MB Intel (64 bit) > 184 0.65 > > > For some reason I never had the memory problems with GROWL or Hardware > Growler. And I never had it with Time machine Growler. I wonder if it > is dependent on certain applications run by others. > > -- > 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. > -- Chris Forsythe @The_Tick <http://twitter.com/The_Tick> -- 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.
