Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac problem - game crashes after 1 minute #333

Closed
Heimbrent opened this issue Dec 23, 2015 · 13 comments
Closed

Mac problem - game crashes after 1 minute #333

Heimbrent opened this issue Dec 23, 2015 · 13 comments

Comments

@Heimbrent
Copy link

This are some collected information before this issue was pruned:

Running RTTR nightly on a Mac crashes seemingly random after starting a game and especially often after burning a building. Different scenarios makes the game crash, but last time I tried to make i crash to save time, and burned up a storage building, 5-10 sec after it crashed. [...] Whatever game I play, it almost never crash at same GF.

Code Type: X86-64 (Native)
OS Version: Mac OS X 10.10.5 (14F1509)
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000026e8
Application Specific Information:
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread ........."

From other run:

/Applications/s25rttr_20151222/s25client.app/Contents/MacOS/rttr.command: line 63: 558 Abort trap: 6 ./bin/s25client "

No useful information in the rttr logs (just normal status entries and the crash itself)

Further report:
6ce5478 crashed even faster (after 1,5 minute), without any possible push from my side.

Test.zip
Issue report from Apple.zip

Flamefire added a commit that referenced this issue Dec 24, 2015
@Flamefire
Copy link
Member

Thread pruned and current information summarized into first post. What would help is someone building a debug version of RTTR on a Mac and executing this (possibly in a debugger) to see at which code line it crashes.

What would also help: RTTR produces replays and logs (possibly in hidden ~/.rttr folder) If you start the replay and play it till the end (you can press 'J' to jump to a GF) and then continue, it should crash right on the next GF. This would be a reproducible crash which should be reported along with the replay and a short description. Then we can fix that.

@hesommer
Copy link

Hi Flamefire,

I've encountered the same problem (even with the latest nightly 20151229). Also burning a building somehow seems to force the crash. I've also noticed that building a fortress forces it too. I would love to build a debug version on my mac. But I'm not sure how to do that. Are there any tutorials how to do that? I would be glad to help cause I love this project and think you guys doing a great job!

@Flamefire
Copy link
Member

All the information are on the main github page: https://github.com/Return-To-The-Roots/s25client
Some help is also in the wiki (check the Wiki link on the github page of RTTR), if you have specific problems, ask in IRC or the forum and someone will help you :)

@Flamefire
Copy link
Member

@Flow86 I just found in the changelog of libSDL (https://www.libsdl.org/release/changes-1.2.html):

Fixed building and running on Mac OS X 10.7 (Lion)

Maybe we should update to 1.2.15 (currently 1.2.14 is used) Is this a problem on the build server?

@Flow86
Copy link
Member

Flow86 commented Dec 31, 2015

the problem I think was, I had to build the libsdl frameworks on a mac with xcode

@Flamefire
Copy link
Member

But it should be worth testing... @hesommer Which version of OSX are you using?

@hesommer
Copy link

@Flamefire: It's the current El Capitan... (10.11.2) - I'll try building it tomorrow...

@Flamefire
Copy link
Member

Ok...
@Flow86: Is it possible to use SDL 2.0 on the build server? According to their homepage there are pre-made builts for OSX and MingGW and Linux versions should be available through the package manager. Migration does not seem to be that hard so if the build server is able to handle it, I'd go to SDL 2.0 and hope, that this fixes the problems with OSx (best guess is, that SDL 1.2.14 might not be compatible with the newer OSx and before going through issues upgrading the build server to 1.2.15 first I'd go directly to 2.0)

@hesommer
Copy link

hesommer commented Jan 1, 2016

Jesus... I'm stuck on making the build... understand too little to fix this error I get when I try to use cmake...

CMake Error at cmake/darwin.cmake:8 (MESSAGE):
woooops: this should not happen! your system has no known architecture!
Call Stack (most recent call first):
CMakeLists.txt:67 (INCLUDE)

hmm... latest cmake, latest xcode... hmm... sorry... If it helps... here is my CMakeOutput.log.zip - Sorry I'm not a programming pro... just trying to help...

@Flamefire
Copy link
Member

The log is incomplete. We need everything from the actual output (all the stuff before that message, including the message itself)

@Flamefire
Copy link
Member

@hesommer Easiest would be to come to IRC and write me directly. I'd be glad to figure this out with your help so compilation and running works on Mac OSX again

@MarcusSt
Copy link
Contributor

Is this still a problem?

@Flamefire
Copy link
Member

Closing as no activity for a year

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants