Closed GoogleCodeExporter closed 8 years ago
The user says he's using version 1.2 of Growl.
Original comment by m...@c-command.com
on 22 Feb 2012 at 8:16
So weird, Growl_HelperAppIsRunning doesn't use GetNextProcess in the 1.3+ SDK,
it uses NSRunningApplication. The only thing I can think of causing this would
be if Growl died in the brief moment between using Growl_HelperAppIsRunning and
this call. GetNextProcess is only used by the weird/ugly legacy support
registration system (Which, admittedly, he would be using with 1.2).
Please have them try upgrading to Growl 1.2.2, as it has numerous bug fixes.
Regardless, we will see what we can do to protect against this in 1.4 SDK
Original comment by dan...@growl.info
on 22 Feb 2012 at 9:02
I just did an "hg clone https://code.google.com/p/growl/" today; that's where I
saw the call to GetNextProcess. Is there some other place where I should be
getting the latest source?
I'll suggest updating to 1.2.2.
Original comment by m...@c-command.com
on 22 Feb 2012 at 9:11
Make sure that you're using the correct 1.3.3 tag. Feel free to swing by #growl
on freenode if you'd like to chat with us. :)
Original comment by ch...@growl.info
on 22 Feb 2012 at 10:47
The user says the exceptions occurred when he was using 1.2.2f1.
Original comment by m...@c-command.com
on 23 Feb 2012 at 12:56
Ask the user try try 1.2.2 and not the fork.
Original comment by ch...@growl.info
on 23 Feb 2012 at 12:59
range exception has been addressed in [7a51c42e78e9], regardless of whether or
not Growl is running it shouldn't cause an exception because the code in
question is in fact assuming that NSRunningApplication is going to return an
array with at least 1 entry in it, and it may very well not.
Original comment by r...@growl.info
on 23 Feb 2012 at 2:27
Original issue reported on code.google.com by
m...@c-command.com
on 22 Feb 2012 at 7:21