Open ian-h-chamberlain opened 6 months ago
Hmm, possibly related to https://github.com/devkitPro/citro3d/issues/35 or https://github.com/devkitPro/citro3d/issues/42 ? Some of the situations described there seem similar, and the reproducing code doesn't use Target::clear
... but adding a clear call doesn't seem like it fixes the lockup, in this case. There might be some other clues there, and with any luck we can change the Rust API to prevent this kind of "misuse" or behavior from happening.
but adding a clear call doesn't seem like it fixes the lockup
Yeah, I tried adding clear calls and other citro3d-sys calls before I made the repo public and it didn't seem to fix it. (I undid those changes before pushing)
Reproducing code is https://github.com/CenTdemeern1/witness-rs/tree/main/frontend-3ds
Deadlock stack trace seems to be this:
Originally posted by @CenTdemeern1 in https://github.com/rust3ds/ctru-rs/discussions/179