-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
[Linux] Segmentation fault on start xr_3da with AMD/ATI GPU #295
Comments
Запускается при откате на cf1329d |
Можете чуть больше рассказать о том, какая видеокарта, какие стоят драйвера (открытые, проприетарные + версия).
|
я как раз пытаюсь бисектнуть. на данный момент этот коммит под подозрением - 2801582 (на bf82cde запускается уверенно, но и так же уверенно падает стоит собственно начать игру, через 1 сек примерно. если нажать выход в меню, выходит но валится в корку... короче дел много). Ubuntu 18.04 остальное всё стандартное из реп Bionic |
@uralets дистрибутив тоже ArchLinux? |
@q4a встроенная Radeon R6,, драйвера открытые, ядро 4.14.88-1-lts
собираю |
2801582 вроде нормальный (собираем-запускаем-новая игра-появляемся-падает) |
падает. дебаг уже завтра. eyes burn(( |
@q4a , опять, но в другом месте Log
GDB
|
У нас в discord-чате ( https://discord.gg/sjRMQwv ) большинство сидит на Nvidia с проприетарными драйверами и на AMD/ATI почти не тестировали. Постараюсь завтра сменить себе видюху и воспроизвести ошибку. |
Not working yet for me either but I am looking forward to running STALKER natively on Linux! |
Падает после выполнения строки
|
It seems to baulk with SIGABRT at strdup.c:42 when no fsgame.ltx is specified on the command line even tho it is in the same dir as the xr_3da executable. |
for me it actually fails at stepping into screen == 0x0 |
GLEW version? Start with key: -use_gl_4.1 |
Glew ver is whatever in ubuntu 18.04 repo |
Start with key: -use_gl_4.1 - will help. |
Чет слишком много магии в этом проекте. Хотябы ключи где-нибудь перечислили... |
Hi there, I've built SDL and mesa to get this shiny backtrace and it says that the bad free happens in gdb backtrace
I don't know if it tries to free something that was allocated in xray or it just interferes with xray's allocator in some way, but after commenting out operator new/delete in https://github.com/OpenXRay/xray-16/blob/xd_dev/src/xrCore/xrMemory.h#L56 I was able to run the game, though I didn't manage to gracefully exit the game or start the new game. |
well it didn't |
Log please |
what exactly do u want me to post? |
Please, don't flood here and write in English here. For Russian discussion we have a special thread: #231 |
This comment has been minimized.
This comment has been minimized.
No, it will not; |
@ivan3182 @uralets @andrew-mcmahon please check if it's fixed (it should be). |
Tomo. Will do. What benefits the TBB mem allocator is supposed to bring anyway? Is it really unfortunate (for performance) to leave it out? |
I will check if it's fixed, compiling now. |
@uralets we can't get rid of it anyways, cause OpenXRay on Windows doesn't work with standard allocation for some reasons, according to guys from Discord. |
Ouch. Windoze sux. Btw its realky quiet on IRC. And its freenode.NET not ORG or am i missing smth? |
I checked it and the issue is gone. Interestingly enough, the binary is still linked against libtbb and libtbbmalloc (possible oversight?) |
Система: ArchLinux
Версия игры: GOG
Коммит: 06bb765
Версии пакетов:
Лог:
GDB:
The text was updated successfully, but these errors were encountered: