Original Post — Direct link

This is what’s in the log just before it crashes and reboots itself:

[2019.03.17-04.02.21:658][516]LogMemory: Platform Memory Stats for WindowsServer [2019.03.17-04.02.21:659][516]LogMemory: Process Physical Memory: 5505.50 MB used, 6380.43 MB peak [2019.03.17-04.02.21:659][516]LogMemory: Process Virtual Memory: 6487.64 MB used, 6795.21 MB peak [2019.03.17-04.02.21:659][516]LogMemory: Physical Memory: 513737.81 MB used, 522923.84 MB total [2019.03.17-04.02.21:659][516]LogMemory: Virtual Memory: 6720.88 MB used, 134217728.00 MB total [2019.03.17-04.02.21:659][516]!!!HANG DETECTED!!! [2019.03.17-04.02.22:359][516] - FPlatformMisc::RequestExit(1) [2019.03.17-04.02.22:359][516]Log file closed, 03/17/19 04:02:22

Anyone have any suggestions on what I can do to fix it if there is a fix because it’s getting really frustrating now. Thanks

External link →
over 5 years ago - /u/wildcardpanda - Direct link

Since the Homestead update the servers are using additional memory, perhaps more than we'd like them to be using which we are aware of and working on addressing. However, the crash you are seeing isn't a memory crash at least not directly anyway nor is it actually a "leak". If you have the option to in your config settings, you can try running your server with -NoHangDetection and see if that prevents it from hanging and eventually closing the server process after ~15 minutes from the hang detection.