Moonbase__

Results 8 comments of Moonbase__

just edited with a log, apologies i thought it wouldnt be useful since .net was the thing crashing

lots of users, also it doesn't even print a new line, it just appears and boom, dead have an image from a time it did happen in docker log

This does also happen without mods. It also happens on a friends server as well. Here's a log without mods [8ac8b2448d35 - 2025.8.27.954 - 2025-08-30 18_43_00.log](https://github.com/user-attachments/files/22063557/8ac8b2448d35.-.2025.8.27.954.-.2025-08-30.18_43_00.log)

> Does this happen when hosting different worlds? Or is it tied to particular world? > > One suspicion I'd have is something in Bepu, which does have native memory...

that tells me that it's definitely something in Bepu then if particles with collisions cause the same crash. perhaps updating it should be put in a higher priority.

i found smthn possibly somewhat related, or at least a clue, a stack overflow in bepu ``resonite-headless | Stack overflow. resonite-headless | at BepuPhysics.Trees.Tree.ComputeBoundsMetric(System.Numerics.Vector3 ByRef, System.Numerics.Vec tor3 ByRef) resonite-headless |...

it might be shadowed cove doing it then since there's constant particles. unless they need to have collisions?

Just wanna update, I haven't had this pop up again since limiting the resources the container could use to 16GB of RAM. Perhaps Bepu has issues with non standard RAM...