Moving a sublevel around while it has a first point of a joint attached causes a panic

[illucc]

Context

In my case i attached a spring to a block, moved it around with the creative thingy (had it break leaves in case that could affect it) and that caused a panic.

Relevant log snippet

thread '<unnamed>' (37559) panicked at /usr/local/cargo/git/checkouts/rapier-b7330b82f1d0b14c/a728067/crates/rapier3d/../../src/dynamics/joint/impulse_joint/impulse_joint_set.rs:403:26:
Internal error: island should be awake.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' (37559) panicked at /rustc/de6d33c033441c5880b863f94d7a3ec8cad141bd/library/core/src/panicking.rs:225:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x7fc3245cdf4a - <unknown>
   1:     0x7fc3245e1e1a - <unknown>
   2:     0x7fc3245d26c2 - <unknown>
   3:     0x7fc3245b58ff - <unknown>
   4:     0x7fc3245c7181 - <unknown>
   5:     0x7fc3245c73eb - <unknown>
   6:     0x7fc3245b59ea - <unknown>
   7:     0x7fc3245ab029 - <unknown>
   8:     0x7fc3245b664d - <unknown>
   9:     0x7fc3245e230d - <unknown>
  10:     0x7fc3245e228b - <unknown>
  11:     0x7fc3245e2417 - <unknown>
  12:     0x7fc32449c378 - Java_dev_ryanhcode_sable_physics_impl_rapier_Rapier3D_step
thread caused non-unwinding panic. aborting.

Crash Report

.

[poohzaza166]

I also have this error aswell. Is there anyway to mitigate this while fix is being work on?
My server is running ubuntu linux in lxc container in proxmox

[AlexIndustrial]

same error. neoforge 1.21.1

[AlexIndustrial]

@poohzaza166 I fixed this by modifying the native library's code. You can use my fork, but do so at your own risk.

https://github.com/AlexIndustrial/sable

[electricsteve]

@AlexIndustrial if you fixed it in your fork, please open a PR. this is the best way to get direct feedback.

[AlexIndustrial]

Of course, I'll do that once I make sure everything is working properly.

[poohzaza166]

@poohzaza166 I fixed this by modifying the native library's code. You can use my fork, but do so at your own risk.

https://github.com/AlexIndustrial/sable

Funny enough I also made my own fork but I haven't post it yet as I am eating my own dog food so to speak on my server what patch did you ended up modified on lib.rs

[electricsteve]

@poohzaza166 I fixed this by modifying the native library's code. You can use my fork, but do so at your own risk.
AlexIndustrial/sable

Funny enough I also made my own fork but I haven't post it yet as I am eating my own dog food so to speak on my server what patch did you ended up modified on lib.rs

You can open their fork and look at the newest commit, that is what they changed.

[Tors-0]

Happened to me just now on Sable 1.2.2 on Linux Mint, neoforge 1.21.1
was on an airship and crashed it into cherry leaves, and as soon as i heard leaves break the game froze and the crash log says thread panic from a similar location as op

Internal error: island should be awake.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' (6473) panicked at /rustc/de6d33c033441c5880b863f94d7a3ec8cad141bd/library/core/src/panicking.rs:225:5:
panic in a function that cannot unwind
stack backtrace:
   0:     0x7f0d96126aca - <unknown>
   1:     0x7f0d9613a99a - <unknown>
   2:     0x7f0d9612b242 - <unknown>
   3:     0x7f0d9610e47f - <unknown>
   4:     0x7f0d9611fd01 - <unknown>
   5:     0x7f0d9611ff6b - <unknown>
   6:     0x7f0d9610e56a - <unknown>
   7:     0x7f0d96103ba9 - <unknown>
   8:     0x7f0d9610f1cd - <unknown>
   9:     0x7f0d9613ae8d - <unknown>
  10:     0x7f0d9613ae0b - <unknown>
  11:     0x7f0d9613af97 - <unknown>
  12:     0x7f0d95ff51ba - Java_dev_ryanhcode_sable_physics_impl_rapier_Rapier3D_step
thread caused non-unwinding panic. aborting.
Process crashed with exitcode 6.