Server Crash dump. Build 1074

Before continuing, please make sure that your issue/crash has not been filed before on this forum. If it has, please provide additional information in the existing forum topic by filling out the template there.

To provide valuable feedback for OneSync issues or crashes, please fill out the following template as much as possible.


Using canary? Yep
Windows version: Windows 10, Fully up to date
System specifications: i7 7700k, 32 Gigs Ram, GTX 1080 SLI


Operating system: Windows 10
Artifact version: 1074
**IP address:**
Resources: ESX Based. 194 resources, can’t be arsed to list them all.
System specifications:
Xeon E3 1270 V3, 4C, 8T CPU. 32 Gigs Ram, 4 TB storage.


Summary: Server crash
Expected behavior: Guess I expected it not to crash?
Actual behavior: Crashed
Steps to reproduce: Run onesync with player slots maxed at 64/64 I guess. nothing special was going on at the time.
Server/Client? Server
Files for repro (if any):
Error screenshot (if any):
.dmp files/report IDs:
3ecd57f0-227b-487a-9b10-805c6dde6d43.dmp (2.0 MB)

Any additional info: We’re running two onesync servers, often with both full. If you have any special sort of error recording / reporting you’d like us to implement, we’d be more than happy to help move the onesync project forward.

Entity weak_ptr becoming invalid, please run servers with procdump -mp -e [PID OF FXSERVER.EXE] C:\dumps attached. Download procdump from Microsoft.

1 Like

Dump was too large for the forum. Heres a google drive link.

This dump is from server version 1080

During this logging period we were experiencing an issue where the server was dropping connections about every hour. Literally just dropped everyone from the server.

Hm - this is the other crash it seems, same as posted on Mini-dump srv crash @ win build 1069 - this one might help to debug that anyway, but not for the crash mentioned in this topic explicitly. :frowning:

Also, big .dmp files compress fairly well - maybe an idea? :stuck_out_tongue: