Closed GoogleCodeExporter closed 8 years ago
Can you attach the output of the console? Open
Applications->Utilities->Console.app
Original comment by loiseau....@gmail.com
on 31 Mar 2010 at 1:04
As mentioned elsewhere, I'm on vacation until the 7th, and will respond as
soon as I can when I get
back.
Original comment by steven.h...@gmail.com
on 31 Mar 2010 at 2:10
As mentioned elsewhere, I'm on vacation until the 7th, and will respond as
soon as I can when I get
back.
Original comment by steven.h...@gmail.com
on 31 Mar 2010 at 2:10
I open Applications->Utilities->Console.app
and then??? srry a bit of a comp. noob
Original comment by randyher...@gmail.com
on 7 Apr 2010 at 1:05
Randy,
With Console open, do whatever it is what causes BlazingStars to crash, and then
immediately switch to Console and copy any line that has a Sender (second
column) of
BlazingStars. They'll look like this:
10-04-07 3:06:36 PM BlazingStars[2967] BlazingStars finished launching.
Copy as many of those as you can see (the newest ones, the ones near the
bottom, are
the most important) into a comment here or into an e-mail to me.
Original comment by steven.h...@gmail.com
on 7 Apr 2010 at 9:22
Hey guys,
For anyone experiencing crashes: I've just integrated a crash reporter into
BlazingStars. You can get it by downloading v 1.0.2, and then when there are
crash
reports to send, BlazingStars will ask you if you want to fire them off to me.
If
you can do that, it will greatly aid me in solving these crashes. Thank you!
Original comment by steven.h...@gmail.com
on 9 Apr 2010 at 10:37
I'm still working on this; I've just got some bug reports that are 10.5.8
(build
9L31), so I think I might have a little more information to work with.
Original comment by steven.h...@gmail.com
on 16 Apr 2010 at 6:22
Hi Steven, I've been using blazingstars a lot now, mass tabeling SNGs.. Only
wondering if you already have a
solution for the problem or know the cause? You should have a lot of my report
messages by now, it crashes
at least twice an hour when I play.
Original comment by randyher...@gmail.com
on 26 Apr 2010 at 2:10
Randy,
I'm aware of the problem, and I have some ideas about its cause; I believe it's
cause by BlazingStars trying to send messages to an Accessibility API element
reference that is no longer valid. I will get to it when I have spare time. I
do
this for free, Randy, and it is not the first priority in my life. It'll get
done
when I can get it done.
Original comment by steven.h...@gmail.com
on 26 Apr 2010 at 4:16
I'm hoping that the memory management changes in 1.0.3 (27) will help with this
issue. I'm having trouble locating the exact source of the problem, though.
Original comment by steven.h...@gmail.com
on 27 Apr 2010 at 9:56
Okay, I think that I've got this one. I was finally able to replicate it, and I
think I've fixed or at least reduced the problem. I'm going to close off this
issue
and let new issues arise as they may.
Original comment by steven.h...@gmail.com
on 30 Apr 2010 at 9:21
Nice! :)
I didn't mean to insult you or anything. Just want to help you to make your
project as good as possible. I
know you do all of this for free and I have great respect for that. Thanks a
lot for doing all of this. I'm sure I
speak for the whole MAC using poker community.
is it already in the downloadable version?
GL and thanks again,
Randy
Original comment by randyher...@gmail.com
on 30 Apr 2010 at 9:35
Randy,
Thanks for the kind words. :) And yes, it's in the newest version 1.0.4 (28).
Original comment by steven.h...@gmail.com
on 30 Apr 2010 at 9:40
Original issue reported on code.google.com by
randyher...@gmail.com
on 30 Mar 2010 at 10:41