Descriptive Problem Summary:
When hosting a game that was built in 509.1310 the server crashs on reboots and restarts
Numbered Steps to Reproduce Problem:
Restart a server
Dream Daemon stops working
Code Snippet (if applicable) to Reproduce Problem:
Does the problem occur:
Every time? Or how often?
Everytime
In other games?
I have only tested that on Pyrce high and SS13 and both of them did the same thing when restarting/rebooting the server
On other computers?
Yes... Yesterday my friend was hosting a game and it had the same proplem
When does the problem NOT occur?
On stable builds
Workarounds: 509.1310 and 509.1309
ID:1972238
Oct 25 2015, 9:24 am
|
|||||||||||||
| |||||||||||||
Oct 25 2015, 11:21 am
|
|
Try building in an earlier version, like 1304. I found a nasty bug in DM 1310 the other night. If it still crashes I'll need more info, like where the crash occurs.
|
So i runned few tests and i found that all builds after Build 509.1307 almost have the same proplem
From Build 509.1308 to Build 509.1310 The proplem happens at randome times while the webcilent is on and yes , randome times... it might stop working and might not stop working Code that was used in Pyrce : Reboot_Server() Code that was used for SS13 : /datum/controller/gameticker/proc/process() And i runned a test on Stable verisons and nothing wrong showed up And i was watching the CPU of both games and SS13 was 3-40% and Pyrce was 0-1% all the time so i do't see it could be a proplem in the CPU So the webcilent might be the main proplem here i think.. |
Again, can you provide info about where it's crashing? 509.1310 would be the best choice for this since it's the most recent, but what I need is a module and offset where the crash occurred. That info should be in your Windows event log.
|
I can't provide any info since windows 10 dosn't have Event logs
but will run a test on 509.1310 and see how everything will go again. |
Same thing happened but i discovred something intersting
Rebooting from the dream daemon (ctrl+R) dosn't stop the server and restarts it very normal and fresh. will try finding a event log software or something like that and give you logs around it anyways. |
I am unable to get this to happen with /tg/station13's code on windows 7.
On both 1310 and 1311. |
In response to Maxsteel13
|
|
Maxsteel13 wrote:
Seems like it is something that only happens on windows 10? Yep...Windows 10 proplem |