Intermittent CPU spike and crash on Growl 1.3.1

[Matt P]

Growl version: 1.3.1
Mac OS 10.7.2
Safari version: 5.1.1

Applications using Growl: Adium (1.5b3), Dropbox (1.1.45), Sparrow
(1.4.2)
(I also use Quickeys, which periodically (every 2 hours) runs an
AppleScript command to invoke Growl, source here: http://pastebin.com/6NmZRZqe)

Every 15 or so minutes, Growl's CPU usage spikes to 100%, until I
mouse over the menu bar icon (I have the Dock icon disabled), at which
point the app usually selfquits. CPU spike continues until quit.

[Charlie S]

They will ask you if you can upload the crash log here

--
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/

[Matt P]

Most recent crashlog:

http://pastebin.com/8Ev4gqi1

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

[Joseph]

Not crashing for me, but using the same versions of Adium and Dropbox
my CPU usage is through the roof until I force quit the growl app. I
don't have the menubar option enabled so I can't try the mouseover.
Truly crippling.

[Christopher Forsythe]

Can you get us a Sample when this happens?

Chris

[John Dyer]

I am seeing the same thing w/ 1.3.1. This is on an MBP i7 w/ 8GB of
memory. Routinly I am seeing Growl w/ 100% cpu as a baseline. Here is
the sample of the running process.

http://dl.dropbox.com/u/177285/growl_sample.txt

[John Dyer]

Yea right now dropbox and growl are using between 160 & 200% of my
cpu. I have restarted Dropbox and Growl but the problem just comes
right back even after Dropbox has caught up... Really frustrating

On Nov 15, 9:43 am, John Dyer <johntd...@gmail.com> wrote:
> I am seeing the same thing w/ 1.3.1.  This is on an MBP i7 w/ 8GB of

> memory.  Routinly I am seeing Growl w/ 100%cpuas a baseline. Here is

> the sample of the running process.
>
> http://dl.dropbox.com/u/177285/growl_sample.txt
>
> On Nov 14, 6:40 pm, Christopher Forsythe <ch...@growl.info> wrote:
>
>
>
>
>
>
>
> > Can you get us a Sample when this happens?
>
> > Chris
>
> > On Mon, Nov 14, 2011 at 3:09 PM, Joseph <jbirthi...@gmail.com> wrote:
> > > Not crashing for me, but using the same versions of Adium and Dropbox

> > > myCPUusage is through the roof until I force quit the growl app.  I

> > > don't have the menubar option enabled so I can't try the mouseover.
> > > Truly crippling.
>
> > > On Nov 11, 11:40 am, Matt P <palmer.s.m...@gmail.com> wrote:
> > > > Growl version: 1.3.1
> > > > Mac OS 10.7.2
> > > > Safari version: 5.1.1
>
> > > > Applications using Growl: Adium (1.5b3), Dropbox (1.1.45), Sparrow
> > > > (1.4.2)
> > > > (I also use Quickeys, which periodically (every 2 hours) runs an
> > > > AppleScript command to invoke Growl, source here:
> > >http://pastebin.com/6NmZRZqe)
>

> > > > Every 15 or so minutes, Growl'sCPUusage spikes to 100%, until I

> > > > mouse over the menu bar icon (I have the Dock icon disabled), at which

> > > > point the app usually selfquits.CPUspike continues until quit.

[Chris George]

Same story here:
http://pastebin.com/cf45JukJ

[Matt P]

Sample as requested:

http://pastebin.com/Jmts7qYA

On Nov 14, 6:40 pm, Christopher Forsythe <ch...@growl.info> wrote:

[John Dyer]

Can we get an update here? This is becoming a MAJOR issue, Really
regretting supporting this project and buying Growl 1.3.1 right now
since it obviously is broken for a lot of people... :(

[Chris Forsythe]

There are only 10 responses on this thread. 3 of those are you John, 2 are Matt. One is Charlie who is helping with emails, and then there's Joseph and George. I don't know that this is affecting a large amount of people. I replied 3 days ago asking for samples, and you guys have provided them. However, you need to be a bit more realistic about time frames here. 

Don't get me wrong, it's an issue, just putting it into perspective based on your email. :)

Anyhow, so we're looking into what you have provided. I'm likely filing a ticket on this shortly.

-- 
Chris Forsythe

[Matt Palmer]

Chris,

I appreciate your time. Bugs are understandable. Thanks for your help.

Matt

[Chris Forsythe]

Thanks, and I appreciate you folks being patient. Some stuff just takes time. :)

-- 
Chris Forsythe

[JediTiger]

See when this happens to me only Growl is the runaway process. Dropbox
and everything else behaves normally.

[Matt Palmer]

It's the same for me – I use DB, but while it may or may not be the cause, it's unaffected as far as CPU/memory usage.

-- 
Matt

[jeffrey wishnie]

I'm seeing the same thing here:

OSX 10.7.2
Growl 1.3.1 from the App Store
Growl Apps: Adium, Dropbox, Skype, Colloquy
MacBook Aluminum (not pro), Core 2 Duo

Spikes to over 100% and stays until quit or killed. I'll post an
ActMonitor log next time it happens

[Chris George]

Also happens on my iMac 11,1 (not just my mid-2010 MBP):

http://pastie.org/private/gilrwbz7rkgbryfty30uq

[Chris George]

Side note: Name's Chris not George ;)

[CC]

Same here. Growl 1.3.1 on MBP Quad I7 2.3/8GB RAM. Growl spikes CPU to
110% sometimes AND uses up to 400 MB Real Memory. I need to force quit
the process and restart Growl to get it back to normal. It does this
every few days at least. Actually the most annoying thing to me is the
fact that it's consistently using up to 400 MB Real Memory (sometimes
higher). I even have the default notifications set, nothing fancy.

On Nov 15, 6:43 am, John Dyer <johntd...@gmail.com> wrote:
> I am seeing the same thing w/1.3.1.  This is on an MBP i7 w/ 8GB of
> memory.  Routinly I am seeing Growl w/ 100%cpuas a baseline. Here is

> the sample of the running process.
>
> http://dl.dropbox.com/u/177285/growl_sample.txt
>
> On Nov 14, 6:40 pm, Christopher Forsythe <ch...@growl.info> wrote:
>
>
>
>
>
>
>
> > Can you get us a Sample when this happens?
>
> > Chris
>
> > On Mon, Nov 14, 2011 at 3:09 PM, Joseph <jbirthi...@gmail.com> wrote:
> > > Not crashing for me, but using the same versions of Adium and Dropbox

> > > myCPUusage is through the roof until I force quit the growl app.  I

> > > don't have the menubar option enabled so I can't try the mouseover.
> > > Truly crippling.
>
> > > On Nov 11, 11:40 am, Matt P <palmer.s.m...@gmail.com> wrote:
> > > > Growl version:1.3.1
> > > > Mac OS 10.7.2
> > > > Safari version: 5.1.1
>
> > > > Applications using Growl: Adium (1.5b3), Dropbox (1.1.45), Sparrow
> > > > (1.4.2)
> > > > (I also use Quickeys, which periodically (every 2 hours) runs an
> > > > AppleScript command to invoke Growl, source here:
> > >http://pastebin.com/6NmZRZqe)
>

> > > > Every 15 or so minutes, Growl'sCPUusage spikes to 100%, until I

> > > > mouse over the menu bar icon (I have the Dock icon disabled), at which

> > > > point the app usually selfquits.CPUspike continues until quit.

[Charlie S]

What display are you using?

[Zac Bowling]

Next time it spikes can you do this?  

• Launch Activity Monitor (/Applications/Utilities/)
• Click on the application to highlight it
• Select View -> Sample Process
• Click Save

Email that sample back to us. We can see what it's doing that has it all hung up and eating CPU that way. 

Zac

[Zac Bowling]

Sorry wrong thread. You already sent a sample :-)

Zac

Sent from my next generation secret iPhone I'm not supposed to talk about. 

On Dec 1, 2011, at 9:44 PM, Charlie S <apple...@gmail.com> wrote:

[jeffrey wishnie]

Here's my Activity Monitor sample:
https://gist.github.com/1424326

This is happening at least once a day. Growl is unusable in this
state. I am going to have to roll back to 1.2.x . A big bummer given
that I paid for the upgrade out of support for the project!

[Stewf]

Same issue here. Sample process: http://up.stewf.com/0N1X0545021R1M1e1T3s

[Oliver Gierke]

Activity monitor report: https://gist.github.com/1433466

I roughly get these spikes 4-5 times a day, have to kill Growl and
restart it :/

[Steffen Behn]

I have exactly the same issue. Its really bothering me right now.

[Avnerus]

Here is my sample.
http://pastebin.com/kmNTczFs
At this stage, Growl was taking ~100% CPU. Clicking the Growl icon at
this stage causes it to crash.

[Jean Baptiste Marquette]

This issue is planetary, and becomes unacceptable for a paid application which has surely passed through the validation process of the Mac App Store. Evidently not enough to give the user (should I say the customer) suitable and stable functionalities…

Cheers

Jean-Baptiste

[Charlie S]

What notification style are you using? 

--
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.

[Tony Arnold]

Hi Guys,

I'm seeing the same on my 2011 MacBook Pro (i7, 8Gb RAM), 10.7.2 — https://gist.github.com/783fd26fba0b1a932ab7

I can kill the process, but it reoccurs pretty much straight away — I've had to leave Growl disabled since this started happening.

all the best,

Tony

[Avnerus]

I use the "Smoke" style.

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

[Charlie S]

Do you have any message in the console that show up when Growl goes wild?

--
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/-/XaTPbHW8xCYJ.

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.

[Stewf]

On Dec 18, 10:56 pm, Charlie S <appleli...@gmail.com> wrote:
> What notification style are you using?

Mono.

[Tony Arnold]

Hi Charlie,

On 20/12/2011, at 5:14 AM, Charlie S wrote:

Do you have any message in the console that show up when Growl goes wild?

No, nothing that would indicate Growl's involvement. Lots of the standard iTunes/Xcode device connect/disconnect bluster, but I don't run anything that monitors that and relays it to Growl. The main thing I run with Growl is GrowlMail.

all the best,

Tony

----------
Tony Arnold
http://thecocoabots.com/

[Christopher Forsythe]

Hey Tony, long time no talk. :)

Can you get a sample, or a few samples? Nobody on the team has been able to reproduce this as of yet, which makes fixing it even harder as you well know.

I've tried running Growl in all sorts of random ways to try to make it hit this condition, but so far I have nothing. I also can't reproduce the high memory issue that we're seeing reports on.

Do you have *any* inclination as to what may be different on your system than my stock core 2 duo/8 gb memory mini? Software configuration, hardware configuration, whatever you can think of that would be relevant could help.

Chris

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.

[Matt Palmer]

Original poster here. The issue has not occurred for me since I applied the most recent MAS update.

-- 
Matt

[Christopher Forsythe]

That's good to hear! What about others? Is anyone who is using 1.3.2 running into this issue?

You can check the version in the About tab.

Chris

[Tony Arnold]

Hi Chris,

On 21/12/2011, at 3:17 AM, Christopher Forsythe wrote:

> Hey Tony, long time no talk. :)
>
> Can you get a sample, or a few samples? Nobody on the team has been able to reproduce this as of yet, which makes fixing it even harder as you well know.
>
> I've tried running Growl in all sorts of random ways to try to make it hit this condition, but so far I have nothing. I also can't reproduce the high memory issue that we're seeing reports on.
>
> Do you have *any* inclination as to what may be different on your system than my stock core 2 duo/8 gb memory mini? Software configuration, hardware configuration, whatever you can think of that would be relevant could help.

Here's the sample:

https://gist.github.com/783fd26fba0b1a932ab7

Unfortunately, I'm as stumped as you guys — I've had a good look at what I'm running that uses Growl, and as yet can't see any rhyme or reason behind it (although I've not looked too hard at the sample at this stage). I'm happy to dig deeper and provide a list of apps and my configuration — if there's anything specific you'd like me to try, please just ask!

[DaveRe]

I'm seeing it on 1.3.2. Also running Dropbox (1.1.45) and
(occasionally) Adium (1.4.3). Adium is generally not running for me
when the issue happens on my machine. I haven't been able to grab a
sample or note the actual memory usage, etc, but I will do so the next
time it happens, and will report back here...

Dave

On Dec 20, 10:25 am, Christopher Forsythe <ch...@growl.info> wrote:
> That's good to hear! What about others? Is anyone who is using 1.3.2
> running into this issue?
>
> You can check the version in the About tab.
>
> Chris
>

> On Tue, Dec 20, 2011 at 10:18 AM, Matt Palmer <palmer.s.m...@gmail.com>wrote:
>
>
>
>
>
>
>
> >  Original poster here. The issue has not occurred for me since I applied
> > the most recent MAS update.
>
> > --
> > Matt
>
> > On Tuesday, December 20, 2011 at 11:17 AM, Christopher Forsythe wrote:
>
> > Hey Tony, long time no talk. :)
>
> > Can you get a sample, or a few samples? Nobody on the team has been able
> > to reproduce this as of yet, which makes fixing it even harder as you well
> > know.
>
> > I've tried running Growl in all sorts of random ways to try to make it hit
> > this condition, but so far I have nothing. I also can't reproduce the high
> > memory issue that we're seeing reports on.
>
> > Do you have *any* inclination as to what may be different on your system
> > than my stock core 2 duo/8 gb memory mini? Software configuration, hardware
> > configuration, whatever you can think of that would be relevant could help.
>
> > Chris
>

[Chris Lauretano]

Add me to the list of people seeing this on 1.3.2. I just woke up to a
MacBook Air that felt like it was on fire.

Kind of funny to use a free application for years without a single
issue, then pay for a new version filled with annoying bugs.

There were no messages in the console during the period in which Growl
entered this state, just the messages when I killed the process


12/22/11 7:16:23.764 AM com.apple.spindump: Growl [173] didn't spin
long enough to report (only 0.9 seconds)
12/22/11 7:16:23.765 AM com.apple.launchd.peruser.501:
([0x0-0xd00d].com.Growl.GrowlHelperApp[173]) Exited: Killed: 9

and the messages when I re-launched:


12/22/11 7:17:36.513 AM Firewall: Growl is listening from
0.0.0.0:23053 proto=6
12/22/11 7:17:36.515 AM Growl: <GCDAsyncSocket: 0x7f804951d870> now
accepting ((null))
12/22/11 7:17:36.612 AM Growl: Setup timer, this should only happen
once
12/22/11 7:17:36.613 AM Growl: Next image check no earlier than 24
hours from 2011-12-22 04:59:00 +0000
12/22/11 7:17:36.910 AM Firewall: Growl is listening from ::ffff:
0.0.0.0:23053 proto=6
12/22/11 7:17:47.973 AM Growl: Deprecated Binding Warning: 'data'
binding of class NSImageView is deprecated. You will only see this
warning once.

Growl is basically configured with default settings since it turns out
it doesn't work with the applications I once used it with, so I don't
really get any notifications.

[DaveRe]

Ok, it happened again. I took a couple of samples and then
killed it. How do I best submit the samples?

In my case, Apple Mail 5.1 was running w/ GrowlMail 1.3.2, and
Dropbox 1.4.5 was also up. Adium was not running.

Dave

[Charlie S]

You attach the samples to a message here

--
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.

--

[Dave Re]

Samples for my version of the issue attached.

Thanks!

Dave

[Chris Forsythe]

Thanks! I have added these to the related ticket:

http://code.google.com/p/growl/issues/detail?id=399

Can you check for crash logs in Console?

-- 
Chris Forsythe

--

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.

Attachments:

- GrowlSample-100% CPU-DaveRe-20111224.txt

- GrowlSample-100%CPU-DaveRe-20111224-Sample2.txt

[Dave Re]

      Chris,

      I have a crash log in Console from 12/4 - that was 1.3.1, though. I can send it on, if that would be useful...

      Dave

--

Dave Re Photography

19104 Ventana Ct, Pflugerville, TX 78660

(c) 512.771.2431 -- (h) 512.251.3815

http://www.daverephoto.com

[Sergey Nebolsin]

Same problem. 

Growl 1.3.2

Mac OS X 10.7.2

Process samples: http://cl.ly/3n2J2n0B3Y250y2h1U15

Cheers

[jason schaad]

Same problem here!

Mac OS X 10.7.2
Growl 1.3.2

I hope there is a fix soon. Too bad, I really liked Growl.

Process samples:
https://docs.google.com/document/d/1qocRNDV21i6h8stZZsgzPsXxWl3oZs4-kgFE3V8cK8E/edit

[Charlie S]

Do you have any style that cause it?  Does it start from a notification from any app?

--
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.

--

[Sven]

I have the same issue. Macbook Air 2010 13" 4GB RAM, Core 2 Duo.
The problem isn't solved in 1.3.2 for me.
I attach the latest crash report I got today when the CPU load spiked
and growl crashed when I clicked on it in the menu.

https://docs.google.com/document/d/1LBJ9B3dLVT1IApmnIbx6kkRKoVSGipDTZB2e44JRGRE/edit

On Dec 26 2011, 7:23 pm, Chris Forsythe <ch...@growl.info> wrote:
> Thanks! I have added these to the related ticket:
>
> http://code.google.com/p/growl/issues/detail?id=399
>
> Can you check for crash logs in Console?
>
> --
> Chris Forsythe
>
>
>
>
>
>
>
> On Sunday, December 25, 2011 at 9:49 PM, Dave Re wrote:
>
> > Samples for my version of the issue attached.
>
> > Thanks!
>
> > Dave
>
> > --
> > 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 (mailto:growld...@googlegroups.com).
> > To unsubscribe from this group, send email to growldiscuss...@googlegroups.com (mailto:growldiscuss...@googlegroups.com).
> > For more options, visit this group athttp://groups.google.com/group/growldiscuss?hl=en.

[dive]

Another sample where Growl eat more that 100% of CPU. It happens every
3-4 days. http://dl.dropbox.com/u/40949784/text/growl_sample_cpu_usage.txt

Growl version 1.3.2, Mac OS X Lion 10.7.2

On Nov 15 2011, 3:40 am, Christopher Forsythe <ch...@growl.info>
wrote:
> Can you get us a Sample when this happens?
>
> Chris
>
> On Mon, Nov 14, 2011 at 3:09 PM, Joseph <jbirthi...@gmail.com> wrote:
> > Not crashing for me, but using the same versions of Adium and Dropbox
> > my CPU usage is through the roof until I force quit the growl app.  I
> > don't have the menubar option enabled so I can't try the mouseover.
> > Truly crippling.

[Fredrik]

I have the same problem. Running Growl 1.3.2 on MB Air 10.7.2 with the following Applications i Growl: Adium Dropbox, Skype, Google+Growl, Growler for Google Notifier.

The Growl process starts to use 100% CPU (on one core) and "hangs". If I do mouse over of the Growl icon in the menu bar both the Growl icon and the process disappears. I can then manually restart the Growl application. 

[Andy]

I'm seeing the same thing with Growl 1.3.2 on my MacBook Air but not on my Mac mini using the same apps on both with Growl (Adium, Dropbox, Itsy, and Sparrow.) 

I'm seeing these an awful in the console:

01/14/12 2:46:19.021 PM Growl: CoreData: error: (21) I/O error for database at /Users/andy/Library/Application Support/Growl/notifications.history.  SQLite error code:21, 'unable to open database file'

01/14/12 2:46:19.022 PM Growl: Core Data: annotation: -executeRequest: encountered exception = I/O error for database at /Users/andy/Library/Application Support/Growl/notifications.history.  SQLite error code:21, 'unable to open database file' with userInfo = {

    NSFilePath = "/Users/andy/Library/Application Support/Growl/notifications.history";

    NSSQLiteErrorDomain = 21;

}

01/14/12 2:46:19.022 PM Growl: Core Data: annotation: -executeRequest: encountered exception = unable to open database file with userInfo = {

    NSFilePath = "/Users/andy/Library/Application Support/Growl/notifications.history";

    NSSQLiteErrorDomain = 14;

}

The whole time those are getting logged itsy is logging this:

01/14/12 3:37:15.651 PM Itsy: <GrowlGNTPNotificationAttempt: 0x10b2a1450> failed because Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0x1001f0430 {NSLocalizedDescription=Read operation timed out}

01/14/12 3:37:15.652 PM Itsy: Failed all attempts at notifying

May be related?

[Charlie S]

What notification style?

On Fri, Jan 13, 2012 at 1:51 AM, Fredrik <fre...@aminoff.eu> wrote:

I have the same problem. Running Growl 1.3.2 on MB Air 10.7.2 with the following Applications i Growl: Adium Dropbox, Skype, Google+Growl, Growler for Google Notifier.

The Growl process starts to use 100% CPU (on one core) and "hangs". If I do mouse over of the Growl icon in the menu bar both the Growl icon and the process disappears. I can then manually restart the Growl application. 

--
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/-/viQ2hHW_H0wJ.

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.

[Fredrik]

I have the standard notification style "Smoke" and have not changed any settings.

[Marko Dolančić]

Was having same issue. Growl 1.3.2. 

Solution that worked for me:

- disabled logging for Skype

- disabled history

Now Growl is running 5days and no more CPU usage spikes :)

Cheers!

[Christopher Forsythe]

So we think we found one of the culprits for this. I need 3-4 people who are experiencing this to email me directly if you're willing to beta test the issue.

This may not be the only culprit, so keep that in mind if you want to volunteer to test the issue.

Chris

On Mon, Jan 16, 2012 at 2:39 AM, Fredrik <fre...@aminoff.eu> wrote:

I have the standard notification style "Smoke" and have not changed any settings.

--

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/-/Qn_B-_luQn0J.

[Sharva Jethwa]

Actually just got fixed

Not sure it might be design issue. But I thought previewing growl style on the left coulmn changes the style. But need to change the default style in the dropdown above

[Joseph]

Still seeing this in 1.3.3.

[Charlie S]

1.4 is in testing

On Mon, Feb 6, 2012 at 8:53 AM, Joseph <jbirt...@gmail.com> wrote:

Still seeing this in 1.3.3.

--
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/-/XlAzJwYH4lgJ.

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 S]

Anything in the console, a style you use and anything happen before the spike

On Fri, Jun 15, 2012 at 4:04 PM, Erik Emri <erik...@gmail.com> wrote:

I am facing the same issue with my MBP.  It seems that Growl is the only run-away process for me as well.  Sometimes it crashes on its own (when I hover over the growl icon in the menubar), and sometimes I have to manually choose to quit it.  It was happening in both Growl 1.3 and now with Growl 1.4.

I run a MBP with OS X 10.7.4

On Friday, 11 November 2011 08:40:53 UTC-8, Matt P wrote:

Growl version: 1.3.1
Mac OS 10.7.2
Safari version: 5.1.1

Applications using Growl: Adium (1.5b3), Dropbox (1.1.45), Sparrow
(1.4.2)
(I also use Quickeys, which periodically (every 2 hours) runs an
AppleScript command to invoke Growl, source here: http://pastebin.com/6NmZRZqe)

Every 15 or so minutes, Growl's CPU usage spikes to 100%, until I
mouse over the menu bar icon (I have the Dock icon disabled), at which
point the app usually selfquits. CPU spike continues until quit.

--

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/-/zM5jAbS4wSMJ.

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 S]

Do you have any messages in the console?

On Sat, Jun 16, 2012 at 2:37 PM, Jonathan Cowperthwait <j...@cowperthwaits.com> wrote:

Hi all; I've got a me-too. 

I'm running Growl 1.4 in 10.7.4 with the following applications hitting Growl:

Adium (1.5.1)

Dropbox (1.4.7)

Grabbox (1.1.7)

Notify (n/v)

I'm using default notification styles, but a set of very old preferences migrated with me across multiple new computers going back at least five years.

Since installing 1.4, I observe that Growl will spike to >100% CPU after approximately 2 hours. It's always the same cores lighting up in the same way (screenshot, of dubious utility, here: http://dl.dropbox.com/u/73197268/Screenshots/5co607kuvhhl.png ) — so when my MacBook fan spins up, I glance at my Activity Monitor display and can instantly recognize the culprit. 

I do not have the Growl toolbar icon, and attempting to access the app by launching its icon from the Applications folder does nothing, but the app does respond to Quit requests from the Activity Monitor.

App sample at time of hang here: http://pastebin.com/XZas3kiA

Inspection of app at time of hang here: http://pastebin.com/9xjc9SEZ

Let me know how I can be of further assistance in data collection; I'd also enthusiastically test any beta fixes if these arise.

--
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/-/-owRk9A8jHAJ.

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.

[Jonathan E Cowperthwait]

Hi Charlie—

Another of these events just occurred; I watched the Console receive updates as it took place. Annotated message log here:

http://pastebin.com/a4nen8Dk

--
/jec.

[Erik Emri]

Hi Charlie - thanks for the note.  Nothing out of the ordinary form a style perspective.  Here is what I see in the console around the time of the "crash".

6/18/12 11:00:22.682 PM Growl: Core Data: annotation: -executeRequest: encountered exception = Updating max pk failed:  with userInfo = {

    NSSQLiteErrorDomain = 14;

}

6/18/12 11:00:22.682 PM Growl: Core Data: annotation: -executeRequest: encountered exception = Updating max pk failed:  with userInfo = {

    NSSQLiteErrorDomain = 14;

}

6/18/12 11:00:22.784 PM Growl: Core Data: annotation: -executeRequest: encountered exception = Updating max pk failed:  with userInfo = {

    NSSQLiteErrorDomain = 14;

}

6/18/12 11:00:25.818 PM Growl: Unresolved error Error Domain=NSCocoaErrorDomain Code=134030 "The operation couldn\U2019t be completed. (NSCocoaErrorDomain error 134030.)" UserInfo=0x7fa0fb1a2650 {NSSQLiteErrorDomain=14, NSUnderlyingException=Updating max pk failed: }, {

    NSSQLiteErrorDomain = 14;

    NSUnderlyingException = "Updating max pk failed: ";

}

6/18/12 11:00:42.681 PM Growl: Core Data: annotation: -executeRequest: encountered exception = Updating max pk failed:  with userInfo = {

    NSSQLiteErrorDomain = 14;

}

Erik.