[BurstCompile(CompileSynchronously = true)] water

[Grandpa Minion]

Version

2.3

Platform

Windows

this burst bug has crashed server multiple times already since 2.3

1. 
   
2. Unity.Burst;
   public struct WaterSimulationApplyFlows : IJobParallelFor
   • WaterSimulationApplyFlows
     Water simulation in specific
     WaterSimulationCalcFlows
     WaterSimulationPostProces
     WaterSimulationPreProcess
     
     
   • This Exception was thrown from a job compiled with Burst, which has limited exception support. Turn off burst (Jobs -> Burst -> Enable Compilation) to inspect full exceptions & stacktraces. In this standalone build configuration burst will now abort the Application.Caught fatal signal - signo:5 code:-6 errno:0 addr:0x3ec00073a90Obtained 21 stack frames.#0 0x007f1e321ab476 in raise#1 0x007f1e339473c0 in PlayerMain(int, char)#2 0x007f1e33947d4b in PlayerMain(int, char)#3 0x007f1e32f99c65 in (Unknown)#4 0x007f1e32f99baf in (Unknown)#5 0x007f1d918c42ff in UnityEngine.Animations.PropertyStreamHandle, UnityEngine.AnimationModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null.GetFloat(UnityEngine.Animations.PropertyStreamHandle*, UnityEngine.AnimationModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null this, UnityEngine.Animations.AnimationStream, UnityEngine.AnimationModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null stream) -> System.Single, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089_8f9b6f65b0da4ea7d984e59263a3e773 from Unity.Animation.Rigging, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null#6 0x007f1d918e60e2 in cfea4edd4d3923f14bbd080d30d59a25_avx2#7 0x007f1d918e8eda in cfea4edd4d3923f14bbd080d30d59a25#8 0x007f1e32f99efb in (Unknown)#9 0x007f1e333a762e in PlayerMain(int, char**)#10

 

[Riamus]

this burst bug has crashed server multiple times already since 2.3

1. 
   
2. Unity.Burst;
   public struct WaterSimulationApplyFlows : IJobParallelFor
   • WaterSimulationApplyFlows
     Water simulation in specific
     WaterSimulationCalcFlows
     WaterSimulationPostProces
     WaterSimulationPreProcess
     
     
   • This Exception was thrown from a job compiled with Burst, which has limited exception support. Turn off burst (Jobs -> Burst -> Enable Compilation) to inspect full exceptions & stacktraces. In this standalone build configuration burst will now abort the Application.Caught fatal signal - signo:5 code:-6 errno:0 addr:0x3ec00073a90Obtained 21 stack frames.#0 0x007f1e321ab476 in raise#1 0x007f1e339473c0 in PlayerMain(int, char)#2 0x007f1e33947d4b in PlayerMain(int, char)#3 0x007f1e32f99c65 in (Unknown)#4 0x007f1e32f99baf in (Unknown)#5 0x007f1d918c42ff in UnityEngine.Animations.PropertyStreamHandle, UnityEngine.AnimationModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null.GetFloat(UnityEngine.Animations.PropertyStreamHandle*, UnityEngine.AnimationModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null this, UnityEngine.Animations.AnimationStream, UnityEngine.AnimationModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null stream) -> System.Single, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089_8f9b6f65b0da4ea7d984e59263a3e773 from Unity.Animation.Rigging, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null#6 0x007f1d918e60e2 in cfea4edd4d3923f14bbd080d30d59a25_avx2#7 0x007f1d918e8eda in cfea4edd4d3923f14bbd080d30d59a25#8 0x007f1e32f99efb in (Unknown)#9 0x007f1e333a762e in PlayerMain(int, char**)#10

You've been here long enough to know that you should post a full log for people to look at. A single error message is often not enough to determine the problem. A link to a discord server (I assume you're spamming your own, though I didn't bother opening the link since it's irrelevant) is not a screenshot or a video or a log.

 

[SpiritChill]

We will need a log and reproduction steps to further assist you have you been able to reproduce this yourself? Are you still experiencing the issue?

 

[SpiritChill]

Hi!

Since there hasn’t been any recent activity on this report, we’ll go ahead and close it for now.

If you run into the issue again in the current stable build, please don’t hesitate to open a new report and include the output log and any helpful details so we can take another look.

Thanks!