Segmentation fault when unpacking DXT5Crunched texture about unitypy HOT 5 OPEN

Thanks for the info.

And, well, this is pretty troublesome then, because the de-crunching is pure Unity code, so bug hunting it will be a nightmare.
The only "simple" solution would be making a python wrapper for the Rust rewrite of the texture2ddecoder, which includes a rewrite of the crunch code. This version is memory safe for sure.
It might take some time until I come around to this though.

from unitypy.

Finished soon™️

from unitypy.

This is a bit tricky to fix, as this is one of the kinds of segfaults that are a bit random and happen only under hard to reproduce conditions. (Or in other words, I can't reproduce the issue, but I see that it could happen due to potato code in dependencies)

Can you check where the segfault happens specifically, during de-crunching or during the texture parsing by PIL?

from unitypy.

I've asked a colleague to test on his PC, and for him everything worked. He is on Windows while I'm on an M1 MacBook Pro. The difference might come from different OS + different architecture (arm vs amd).
I will try to debug ASAP to tell you from which line it's coming.

PS: Sorry for the delay, I didn't get any notification.

from unitypy.

Can you check where the segfault happens specifically, during de-crunching or during the texture parsing by PIL?

The segfault happens during de-crunching on this line

from unitypy.