search

edisona / endgame-singularity

Automatically exported from code.google.com/p/endgame-singularity
1 stars 0 forks source link

0.30 mac application crash after choosing difficulty #65

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Open Endgame Singlularity
2. Choose Normal Difficulty
3. Application Crashes
4. The next time application is opened, it crashes before reaching "choose"
screen.

Repeat

Running Mac OS X 10.5.6. Previous versions have worked for me.

Original issue reported on code.google.com by Durandal...@gmail.com on 27 Jan 2009 at 2:22

GoogleCodeExporter commented 9 years ago 
Try adding 'daynight = True' to prefs.dat.  Although a crash before you even 
get to
pick the difficulty is worrisome.  Anyone know how to see the Python stack 
trace on
Mac OS X?

Original comment by phil.bor...@gmail.com on 27 Jan 2009 at 2:32

GoogleCodeExporter commented 9 years ago 
Obviously my brain is not working tonight.  Set it to False, not True.  I'm 
still not
convinced that that'll fix a crash directly on the main menu, though.

Original comment by phil.bor...@gmail.com on 27 Jan 2009 at 2:35

GoogleCodeExporter commented 9 years ago 
> Anyone know how to see the Python stack trace on Mac OS X?

Open Macintosh HD -> Applications -> Utilities -> Console, there should be an 
entry
somewhere in there for "Endgame Singularity.app".

Original comment by funnyman3595 on 27 Jan 2009 at 2:40

GoogleCodeExporter commented 9 years ago 
==I open the program==

1/26/09 9:46:30 PM com.apple.launchd[91]
([0x0-0x29b29b].org.pythonmac.unspecified.EndgameSingularity[2382]) Exited
abnormally: Abort trap 
1/26/09 9:46:58 PM Endgame Singularity[2392] Warning once: This application, or 
a
library it uses, is using NSQuickDrawView, which has been deprecated. Apps 
should
cease use of QuickDraw and move to Quartz. 

==I click New Game, I choose a difficulty==

1/26/09 9:46:58 PM Endgame Singularity[2392] Warning once: This application, or 
a
library it uses, is using NSQuickDrawView, which has been deprecated. Apps 
should
cease use of QuickDraw and move to Quartz. 
1/26/09 9:47:21 PM 
[0x0-0x29c29c].org.pythonmac.unspecified.EndgameSingularity[2392]
Endgame Singularity(2392,0xa0196720) malloc: *** error for object 0x916a911c:
Non-aligned pointer being freed 
1/26/09 9:47:21 PM 
[0x0-0x29c29c].org.pythonmac.unspecified.EndgameSingularity[2392]
*** set a breakpoint in malloc_error_break to debug 
1/26/09 9:47:21 PM 
[0x0-0x29c29c].org.pythonmac.unspecified.EndgameSingularity[2392]
Endgame Singularity(2392,0xa0196720) malloc: *** error for object 0xc0000003:
Non-aligned pointer being freed 
1/26/09 9:47:21 PM 
[0x0-0x29c29c].org.pythonmac.unspecified.EndgameSingularity[2392]
*** set a breakpoint in malloc_error_break to debug 
1/26/09 9:47:21 PM 
[0x0-0x29c29c].org.pythonmac.unspecified.EndgameSingularity[2392]
Endgame Singularity(2392,0xa0196720) malloc: *** error for object 0x12f32170:
Non-aligned pointer being freed (2) 
1/26/09 9:47:21 PM 
[0x0-0x29c29c].org.pythonmac.unspecified.EndgameSingularity[2392]
*** set a breakpoint in malloc_error_break to debug 
1/26/09 9:47:21 PM 
[0x0-0x29c29c].org.pythonmac.unspecified.EndgameSingularity[2392]
Fatal Python error: (pygame parachute) Bus Error

Original comment by Durandal...@gmail.com on 27 Jan 2009 at 2:48

GoogleCodeExporter commented 9 years ago 
But you're right, if I choose to turn day/night off in the GUI preferences, the 
game
starts correctly

Original comment by Durandal...@gmail.com on 27 Jan 2009 at 2:52

GoogleCodeExporter commented 9 years ago 
I got the same crash here.
I download the source for Linux (i got pygame installed) and the game run fine 
on Mac from Source.

I also develop with pygame for mac and i encounter a crash with my bundled app 
(py2app) that seems related. 
For my game it crash at run. I finally found a way to bypass the crash : 
install back pygame 1.8.0 made the app 
(py2app) works fine. using pygame 1.8.1 with pyapp made the app to crash...

Original comment by padora...@gmail.com on 27 Jan 2009 at 6:24

GoogleCodeExporter commented 9 years ago 
Yeah, something's going wonky with py2app and NumPy.  Not sure why pygame 1.8.0 
would
work, but there's a nasty sound bug in that version, so we really don't want to 
use it.

Original comment by funnyman3595 on 31 Jan 2009 at 10:18

GoogleCodeExporter commented 9 years ago

Original comment by funnyman3595 on 31 Jan 2009 at 10:19

GoogleCodeExporter commented 9 years ago 
Is this still an issue with pygame 1.9.x? It was released in 2009, so I doubt 
1.8.1 is used anymore. If app works fine with latest stable pygame, then 
problem fixed :)

Can anyone check?

Original comment by singular...@rodrigosilva.com on 20 Dec 2012 at 2:27