Support Board
Date/Time: Fri, 22 Nov 2024 21:25:08 +0000
Post From: Linux
| [2020-09-27 12:48:43] |
| User921987 - Posts: 236 |
|
It seems this is a bug of X11 and if I remember right (?!) there is no active issue in X11 development -> https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues (or do you see there anything similar?) Anyway what I understand the origin of the problem is in the way of how some objects are handled badly (not thread-safe) in the X11 client library code. So lowering the # of CPU cores to 1 at startup will remove the thread-safe problem at startup but lifting the number of cores back later should put the system back to the state where the bug can activate later... My system crashed at the startup and also later during the normal program execution but using taskset I am able to run SC without any problems. It's just slower. This is why I am trying to find a solution where I don't have to use taskset. But this all is just my quessing game because I have not debugged the bug in the code by myself. I've just read about it from the code fix made by others. So there is still possibility that your workaround is valid too. btw. I have been "stress testing" now the new library code about 24 hours without any problems (without taskset). Also a new Wine version 5.18 popped out few days ago. Im using it. EDIT: I wrote an email for Jacek let's see if he can give any new information for us. Date Time Of Last Edit: 2020-09-27 14:52:25
|