-
-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault when unpacking DXT5Crunched texture #214
Comments
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? |
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). PS: Sorry for the delay, I didn't get any notification. |
The segfault happens during de-crunching on this line UnityPy/UnityPy/export/Texture2DConverter.py Line 128 in 99c240c
|
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. |
Code
Error
This error is happening on the line
img = data.image
Bug
The image should be read successfully without crashing the whole script. When I checked
m_TextureFormat
attribute, the returned value was29
. I've tried with others tools like AssetRipper, and they can extract everything without issue. Also, I tried to disable the C-typetree reader, but the segmentation fault is still occurring.To Reproduce
my_asset_bundle.zip
I zipped the file to make GitHub accepts it. You need to unzip it first.
The text was updated successfully, but these errors were encountered: