Crash in pokerWindowIsActive

[GoogleCodeExporter]

I'm getting crash reports highlighting a problem in the HKWindowManager
code, which go something like this:

Thread 0 Crashed:
0   libobjc.A.dylib                 0x92bef688 objc_msgSend + 24
1   ...ullyfunctional.blazingstars  0x0000a0fd -[HKWindowManager
pokerWindowIsActive] + 51
2   ...ullyfunctional.blazingstars  0x0000a017 -[HKWindowManager
windowFocusDidChange] + 27

I suspect that this might have something to do with Spaces, but I haven't
been able to nail it down yet.  Interestingly, every report (out of about a
dozen I've gotten so far) are all running OS X 10.5.8;  if anyone running
Snow Leopard gets this crash, please send me the logs (download v1.0.2 for
the automated crash reporter!), because the 10.6 logs have more information
in them.

Original issue reported on code.google.com by steven.h...@gmail.com on 11 Apr 2010 at 11:05

[GoogleCodeExporter]

I've sended like 3 or 4 reports so far.. It doesn't allow me to send it every 
time it crashes though..

Original comment by randyher...@gmail.com on 13 Apr 2010 at 11:52

[GoogleCodeExporter]

The crash reporter has to wait until the OS writes the crash log to the logs 
directory, and this doesn't 
always happen instantaneously. If you restart BlazingStars right away, the 
crash reporter may not be able 
to immediately access the crash log, but it will next time. 

My biggest problem right now is that I don't have a Leopard machine to nail 
down this particular problem;  
I guess I'll just have to start shotgunning it and see what happens. 

Original comment by steven.h...@gmail.com on 13 Apr 2010 at 1:47

[GoogleCodeExporter]

See Issue 63;  I believe that I've fixed it.  

Original comment by steven.h...@gmail.com on 30 Apr 2010 at 9:22

• Changed state: Fixed