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

Consistent crash whilst loading specific save games #896

Open
ghost opened this issue Dec 10, 2016 · 2 comments
Open

Consistent crash whilst loading specific save games #896

ghost opened this issue Dec 10, 2016 · 2 comments

Comments

@ghost
Copy link

ghost commented Dec 10, 2016

Operating system and version:
(Arch) Linux 64-bit, OpenJK (JK2) built from Git master on 19 November.

Is this for single player or multiplayer?
Single player.

Description of the bug (and if possible, steps to reproduce the bug):
Loading save games in JK2 SP crashes sometimes. Loading other (previous) saves, however, works. What's also strange is that everytime this happens, when reloading and in the case of quicksaves, I get an incorrect screenshot (i.e. of a place I quicksaved before). Almost as if the game failed to quicksave and it's giving me an old quicksave. The loading screen with the old image then pops up, waits about a second, and then crashes.

I've also attached an autosave that exhibits a consistent crash here whilst trying to load it. auto.zip

EDIT: It turns out saving in the level cairn_assembly is entirely broken for me. Previously I sometimes had saves that I couldn't load and could get by by loading another save and continuing from there, but loading an older save in this level and then moving to the part where the floor is electrified, saving there, and finally reloading consistently crashes the game again for me. It seems I'm now stuck in this level (or perhaps finishing it in one go without reloading will work ;-)).

Dump:

Process 26620 (openjo) of user 1002 dumped core.

Stack trace of thread 26620:
#0  0x00007f3fee8ff585 n/a (/opt/openjk-git/JediOutcast/OpenJK/jospgamex86_64.so)
#1  0x00007f3fee9c4b64 n/a (/opt/openjk-git/JediOutcast/OpenJK/jospgamex86_64.so)
#2  0x00007f3fee873f25 n/a (/opt/openjk-git/JediOutcast/OpenJK/jospgamex86_64.so)
#3  0x00007f3fee87c535 n/a (/opt/openjk-git/JediOutcast/OpenJK/jospgamex86_64.so)
#4  0x00007f3fee87ffff n/a (/opt/openjk-git/JediOutcast/OpenJK/jospgamex86_64.so)
#5  0x00007f3fee8e912e n/a (/opt/openjk-git/JediOutcast/OpenJK/jospgamex86_64.so)
#6  0x00007f3fee8b8539 n/a (/opt/openjk-git/JediOutcast/OpenJK/jospgamex86_64.so)
#7  0x00007f3fee8bb5c2 n/a (/opt/openjk-git/JediOutcast/OpenJK/jospgamex86_64.so)
#8  0x0000000000409920 n/a (openjo_sp.x86_64)
#9  0x00007f40128ad291 __libc_start_main (libc.so.6)
#10 0x000000000040b74a n/a (openjo_sp.x86_64)

Stack trace of thread 26622:
#0  0x00007f401296c551 ppoll (libc.so.6)
#1  0x00007f400883899d pa_mainloop_poll (libpulse.so.0)
#2  0x00007f4008838f8e pa_mainloop_iterate (libpulse.so.0)
#3  0x00007f4008839040 pa_mainloop_run (libpulse.so.0)
#4  0x00007f401262ae2f n/a (libSDL2-2.0.so.0)
#5  0x00007f40125f02dc n/a (libSDL2-2.0.so.0)
#6  0x00007f401263f8a9 n/a (libSDL2-2.0.so.0)
#7  0x00007f40116a0454 start_thread (libpthread.so.0)
#8  0x00007f40129757df __clone (libc.so.6)

Stack trace of thread 26623:
#0  0x00007f401296c551 ppoll (libc.so.6)
#1  0x00007f400883899d pa_mainloop_poll (libpulse.so.0)
#2  0x00007f4008838f8e pa_mainloop_iterate (libpulse.so.0)
#3  0x00007f401262ac6f n/a (libSDL2-2.0.so.0)
#4  0x00007f401258d72b n/a (libSDL2-2.0.so.0)
#5  0x00007f40125f02dc n/a (libSDL2-2.0.so.0)
#6  0x00007f401263f8a9 n/a (libSDL2-2.0.so.0)
#7  0x00007f40116a0454 start_thread (libpthread.so.0)
#8  0x00007f40129757df __clone (libc.so.6)

Good thing I save multiple times!

What did you expect to happen instead?
The save would load correctly without crashing.

@ensiform
Copy link
Member

ensiform commented Dec 10, 2016

If your saves were made at some point during OpenJK (JK2) development they have been invalidated because we now restored basejk2 save support. I realize it shouldn't crash but if you can try getting it to crash consistently with newest git and new saves only please get back to me. The stack trace is appearing to miss any relevant data of where the crash is happening in the gamecode.

JK2 has been on the backburner for the most part for a while too.

@ghost
Copy link
Author

ghost commented Dec 10, 2016

That is understandable. I've however not updated my OpenJK since I built it at the mentioned date and have started the single player campaign completely anew from it, so I think these are new saves on the new version.

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

No branches or pull requests

1 participant