03-23-2013, 08:01 AM
(This post was last modified: 03-23-2013, 08:07 AM by MirceaKitsune.)
Since a few weeks ago, I started experiencing severe system crashes when running Xonotic. After a few hours of opening and closing Xonotic, the game suddenly freezes as you play, and the operating system becomes unusable and unrecoverable. The computer has to be force restarted and sometimes after I log back in, I notice the crash corrupted settings of existing programs and caused data loss. Those are the things I know so far:
- It's a known issue with the fglrx (proprietary ATI) driver on Linux, though the exact cause is not yet known.
- Disabling r_glsl_skeletal reduces the problem but doesn't fix it. With it I had approximately 4 crashes a day, now I have about 1.
- It only happens after approximately 6 hours since starting up the system, and / or starting up Xonotic and closing it for more than approximately 6 times.
- The freeze takes place when new models or textures are loaded into the view. For example, if a player spawns behind a wall then you move past that wall and see it for the first time. It also happens when selecting the Laser after holding the Shotgun (for the first time since starting Xonotic). Note that at first the freezes were happening in the menu (before even loading a map).
- I noticed that normally, whenever viewing a model for the first time, Xonotic freezes for just a moment (without causing any damage) and messages are printed in the console in cyan saying "GLSL shader compiled" or something like that. I'm imagining it might be related to that, and at some point a GLSL shader breaks and somehow kills the whole system.
- Once Xonotic freezes, the entire OS becomes unusable. Not even the num lock / caps lock / scroll lock keyboard leds can be toggled any more, and you can't even switch to a system console using control + alt + f#.
This is a very major issue and threatening to the whole operating system, and I believe it should be fixed urgently. Unfortunately I can't do much debugging since the computer gets broken once the problem happens. If there is anything I can do to further debug it however let me know. divVerent suggesting I try remote desktop with SSH while it's stuck, but I don't know how to set that up so no overly advanced stuff please.
Until it's fixed, are there any cvars you suggest changing or ideas on how to prevent the crashes, and perhaps recover the machine without hard restarting?
- It's a known issue with the fglrx (proprietary ATI) driver on Linux, though the exact cause is not yet known.
- Disabling r_glsl_skeletal reduces the problem but doesn't fix it. With it I had approximately 4 crashes a day, now I have about 1.
- It only happens after approximately 6 hours since starting up the system, and / or starting up Xonotic and closing it for more than approximately 6 times.
- The freeze takes place when new models or textures are loaded into the view. For example, if a player spawns behind a wall then you move past that wall and see it for the first time. It also happens when selecting the Laser after holding the Shotgun (for the first time since starting Xonotic). Note that at first the freezes were happening in the menu (before even loading a map).
- I noticed that normally, whenever viewing a model for the first time, Xonotic freezes for just a moment (without causing any damage) and messages are printed in the console in cyan saying "GLSL shader compiled" or something like that. I'm imagining it might be related to that, and at some point a GLSL shader breaks and somehow kills the whole system.
- Once Xonotic freezes, the entire OS becomes unusable. Not even the num lock / caps lock / scroll lock keyboard leds can be toggled any more, and you can't even switch to a system console using control + alt + f#.
This is a very major issue and threatening to the whole operating system, and I believe it should be fixed urgently. Unfortunately I can't do much debugging since the computer gets broken once the problem happens. If there is anything I can do to further debug it however let me know. divVerent suggesting I try remote desktop with SSH while it's stuck, but I don't know how to set that up so no overly advanced stuff please.
Until it's fixed, are there any cvars you suggest changing or ideas on how to prevent the crashes, and perhaps recover the machine without hard restarting?
