-
Notifications
You must be signed in to change notification settings - Fork 2.3k
[Bug]: Conan Exiles server keeps crashing #2692
Comments
Those what you call errors is winetrickd because the docker image indeed went to wine 9. But that should not cause any issues. |
Strange... We also tried increasing RAM but that just increased the crash time... It was working before the update but now it seems broken. Like said we tried setting up a new server but it was the same. |
Having the same issue here. Kicks after 10-15 minutes or so. |
Then for now revert to a older version of the latest wine image that still has 8 |
Would you be so kind and send me more Info on how to do this? Kinda new to this and trying to learn. |
Same, please. I'm not sure how to do that either |
A fix for now.
|
Its working for me again. Thank you :) |
Same! Up for 16h straight now. Thank you kindly! |
I tried running it ourside of pterodactyl with wine 9.0 and it behaves the same. So it is definetly a wine bug.
This huge amount of RAM usage in the logs might be an indicator for the erronous behaviour. |
Then report it to Wine Team. Was the same with wine 8 ;) A hugh usage of RAm since an update ;) btw; your posted line says nothing. Post a better log for using too much RAM. My installation stays on 4 till 8 gb RAM with Wine 9 |
Panel Version
1.11
Wings Version
1.11
Service
Conan Exiles
Modified
No, not modified
Expected Behavior
Server should run without the console beeing flooded with wine warnings.
Actual Behavior
Since the last update (we think its wine 9.0 thats causing this) the server does not behave like expected. It boots normally but with wine prefix warnings:
At this point you are able to connect and play. But after round about 10-15 minutes you will get kicked because of RAM problems and the server restarts. We tried to setup a new server but the behaviour is the same.
Steps To Reproduce
Step 1: latest version
Step 2: install and keep running
Step 3: crash and reboot
Install logs
https://pteropaste.com/t9dgyej5mmsn
The text was updated successfully, but these errors were encountered: