This object is in archive! 

Urgent: DS keeps crashing suddenly!

Fowlplaychiken shared this bug 5 years ago
Won't Fix

Keeps crashing suddenly this evening. No minidump, and crash is total - client just closes entirely and does not try to re-open.


19:12:07.3588 [ERROR] Keen: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at hkpWorld.removeEntityBatch(hkpWorld* , hkpEntity** , Int32 ) at Havok.HkWorld.FinishBatch() at VRageMath.Spatial.MyClusterTree.ReorderClusters(BoundingBoxD aabb, UInt64 objectId) at VRageMath.Spatial.MyClusterTree.EnsureClusterSpace(BoundingBoxD aabb) at Sandbox.Engine.Physics.MyPhysics.EnsureClusterSpace() at Sandbox.Engine.Physics.MyPhysics.Simulate() at UpdateComponents_0(Object ) at Sandbox.Game.World.MySession.Update(MyTimeSpan updateTime) at Sandbox.MySandboxGame.Update() at Sandbox.Engine.Platform.Game.UpdateInternal() at RunSingleFrame_0(Object ) at Sandbox.Engine.Platform.FixedLoop.<>cDisplayClass1.<Run>b0() at Sandbox.Engine.Platform.GenericLoop.Run(VoidAction tickCallback) at Sandbox.Engine.Platform.Game.RunLoop() at Sandbox.MySandboxGame.Run(Boolean customRenderLoop, Action disposeSplashScreen) at Torch.VRageGame.DoStart() at Torch.VRageGame.Run() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()


https://cdn.discordapp.com/attachments/301835879947698177/492111045003968522/Keen-2018-09-19.log


No minidump


https://cdn.discordapp.com/attachments/301835879947698177/492111046455328788/connection_log_27017.txt

Replies (4)

photo
1

Hello,

Thank you very much for your feedback. Please, can you upload here a world, which causes this issue?

Have a nice day :-)


Kind Regards

Keen Software House: QA Department

photo
1

I fixed the bug. Took 6hr to find and fix cause; an asteroid file somewhere became corrupt and caused crash whenever going near it, and whenever bringing server down. Game would try to close the file after autosave and die. Voxel reset did not fix it; but manually deleting all asteroid files did.


Here is the full game file from before I fixed the bug:


https://drive.google.com/open?id=1ucq3ml_4nnLN43GaGxqSDcSUqNauwSjc


Note you can open in Vanilla launcher or in Torch; bug persists. Oldest reference online to this same error code is also 2015; so its an old one.


To remove all the safezones, go to the storage folder in the instance-gamesave folder and set safezones to false in the config for the mod. Useful to remove the offline safezone protection when loading the world for testing.


Here is a GPS close to the bugged corrupted asteroid. Players crashed the server when entering sync range of it; in addition to the server crashing on shutdown or restart right after successful autosave.


GPS:Cancer:71393.9:106472.55:-121369.78:

photo
1

It would be useful to upload just save of the world, not whole game. We don't use torch.

Thank you very much and it is nice you fixed the issue.


Kind Regards

Keen Software House: QA Department

photo
1

I loaded it up in Vanilla client with same results. If you guys can pull the same files? They are the same.


I will upload just the save next time.


Thanks for looking! This serious bug has been around since 2015 (well prior to Torch) and I believe this is the first case someone has produced a before-fix world-save, known the actual cause of the issue, the geographic area of the issue, and steps to fix the issue. Hoping the QA allows you guys to finally fix this one! :) Thank you for all you do.

photo
1

The uploaded file no longer exists,

please create a new ticket if the issue still persists on version 196.016


Closing this one as Won't fix.


Keen QA

Replies have been locked on this page!