Bug after update

24 views
Skip to first unread message

freshh29

unread,
Jun 12, 2012, 8:15:42 PM6/12/12
to Growl Discuss
Newest Lion
Newest Growl MAS

After newest Update from time to time my MAC runs hot while Mac need
100 % of CPU... this is the 3 rd day

It don't stop from alone. I must end Growl...and restart then works
fine for few hours

Please fix

Warren Ockrassa

unread,
Jun 12, 2012, 10:14:36 PM6/12/12
to Growl Discuss
Same problem here. The update has NOT fixed the 100% CPU problem.

TJ Luoma

unread,
Jun 13, 2012, 1:40:04 AM6/13/12
to growld...@googlegroups.com


On Tue, Jun 12, 2012 at 10:14 PM, Warren Ockrassa <wock...@gmail.com> wrote:
Same problem here. The update has NOT fixed the 100% CPU problem.

Just as a data point: I have never seen this. Which isn't to say that it isn't happening to others, but, by the same token, it isn't universal.

FWIW

TjL


Charlie S

unread,
Jun 13, 2012, 10:46:27 AM6/13/12
to growld...@googlegroups.com
Anything in the console just before the cpu spike?



--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.



--


----
Charlie Schloss

Grab Opera the fastest browser on earth @
http://my.opera.com/community/download.pl?ref=Chas4&p=opera_desktop


Why Open the Web?

Despite the connecting purpose of the Web, it is not entirely open to all of
its users. When used correctly, HTML documents can be displayed across
platforms and devices. However, many devices are excluded access to Web
content.

http://my.opera.com/community/openweb/info/


freshh29

unread,
Jun 13, 2012, 3:46:41 PM6/13/12
to growld...@googlegroups.com
No nothing

freshh29

unread,
Jun 13, 2012, 3:48:10 PM6/13/12
to growld...@googlegroups.com
Sorry yes .... i have 5 Report in console for Growl


Am Mittwoch, 13. Juni 2012 02:15:42 UTC+2 schrieb freshh29:

Daniel Siemer

unread,
Jun 13, 2012, 5:45:19 PM6/13/12
to Growl Discuss
We know the source of this bug, however, getting it fixed was going to
take much longer than we had for 1.4 due to the sandboxing deadline,
and 1.4 has a number of fixes and improvements that needed to ship.
The best stop gap for now is to quit or force quit growl and relaunch
it when it starts doing it. We got into this situation by not being
careful enough with the design and implementation of the previous
networking stack, so we are going to take the time we need to make
sure its right this time. Growl 2.0 is the intended target for the
new networking stack.

Christopher Forsythe

unread,
Jun 19, 2012, 1:36:44 AM6/19/12
to growld...@googlegroups.com
Ya, unfortunately this is still an issue in 1.4. We're working on correcting the problem.


-- 
Chris Forsythe

On Wed, Jun 13, 2012 at 1:36 PM, Michael Crawford <dal...@gmail.com> wrote:
I have had this same issue.    Happens even if Growl is paused.

--
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/-/jUc6kd7iN3YJ.
Reply all
Reply to author
Forward
0 new messages