Bug #534
Segmentation Fault after resources are loaded at launch
100%
Description
Operating System: Gentoo Linux
Processor: 64-bit Intel Core 2 Duo
Problem: Program closes with Segmentation Fault after resources are loaded.
Details: If I launch KSP (32-bit and 64-bit versions both have this problem), the resource loading screen completes, but the game crashes with a segfault immediately afterward. I get a split second of the "send data" prompt before it closes. This is on a fresh installation on 0.19.1. The problem did not exist in 0.19.0.
History
#1 Updated by Ted over 11 years ago
Could you attach the player.log found at .config/unity3d/Squad/Kerbal Space Program/ to this issue?
Thanks.
#3 Updated by bl4qkubartnndfhr over 11 years ago
I'm having a similar issue. Here is a stack trace.
---Type <return> to continue, or q <return> to quit---
Program received signal SIGXCPU, CPU time limit exceeded.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7fcf800 (LWP 6699)]
0x00007ffff67cede6 in r600_set_sampler_views.isra.15 () from /usr/lib64/dri/r600_dri.so
(gdb) bt
#0 0x00007ffff67cede6 in r600_set_sampler_views.isra.15 () from /usr/lib64/dri/r600_dri.so
#1 0x00007ffff6601b18 in update_textures () from /usr/lib64/dri/r600_dri.so
#2 0x00007ffff65fdcf7 in st_validate_state () from /usr/lib64/dri/r600_dri.so
#3 0x00007ffff66045da in st_Clear () from /usr/lib64/dri/r600_dri.so
#4 0x00000000005759c1 in ?? ()
#5 0x000000000057dfa3 in ?? ()
#6 0x00000000005b4ead in ?? ()
#7 0x000000000087db9c in ?? ()
#8 0x0000000000b4d303 in ?? ()
#9 0x0000003dd6821a05 in __libc_start_main () from /lib64/libc.so.6
#10 0x0000000000456669 in ?? ()
#11 0x00007fffffffde78 in ?? ()
#12 0x000000000000001c in ?? ()
#13 0x0000000000000001 in ?? ()
#14 0x00007fffffffe1c7 in ?? ()
#15 0x0000000000000000 in ?? ()
(gdb) continue
Continuing.
Detaching after fork from child process 19546.
Program received signal SIGABRT, Aborted.
0x0000003dd6835ba5 in raise () from /lib64/libc.so.6
(gdb) continue
Continuing.
[Thread 0x7ffff4084700 (LWP 6768) exited]
[Thread 0x7ffff4186700 (LWP 6746) exited]
[Thread 0x7fffecd5b700 (LWP 6745) exited]
[Thread 0x7fffed55c700 (LWP 6744) exited]
[Thread 0x7fffeeb77700 (LWP 6713) exited]
[Thread 0x7fffef378700 (LWP 6712) exited]
[Thread 0x7fffefb79700 (LWP 6710) exited]
[Thread 0x7ffff49c7700 (LWP 6709) exited]
[Thread 0x7ffff71d8700 (LWP 6706) exited]
[Thread 0x7ffff7269700 (LWP 6705) exited]
[Thread 0x7ffff7fcf800 (LWP 6699) exited]
Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb)
#4 Updated by Ted over 11 years ago
- Category set to Gameplay
#5 Updated by sr over 11 years ago
Is the issue still happening with the current 0.21 version?
#6 Updated by mattakaslash over 11 years ago
No, I'm able to use version 0.21.1 without issue.
#7 Updated by Ted over 11 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Okay, thanks. Please contact me if it occurs again and you need it opened.