jpg cmyk image causes a crash#554

Getting a bizarre Unity Crash when trying to load in a custom card with the attached image.

The crash appears specific to the image: Viewing the image online is no problem. Downloading it to my machine and viewing it with whichever image-viewer is no problem. Using the image (locally, or uploading to cloud) to make a custom card by hand causes the Unity crash in TTS. Just uploading it to the cloud causes the crash (I suggest not repeating, TTS crashes whenever I try to view the cloud files).

Player.log of the crash is attached.

benjamin_dobell on the TTS/scripting discord server pointed out:
“They look like valid JPEG. However, most JPEGs are sRGB colorspace. They’re CMYK. Maybe somehow causing issues”
https://discord.com/channels/342471570955960324/368208369812504587/818441833692004372

Indeed, the image appears to be using CMYK color format without having the format properly labeled in the file’s meta-data.
On one hand, one could say that it’s a bad/corrupt image.
One the other hand, these sort of images aren’t uncommon, and most image viewers handle them without any problems, e.g. viewing the attached image here via chrome/or-whatever.

I’ve seen this as well, an unfortunate user uploaded one into their steam cloud so the in-game cloud viewer crashed (they opted to wipe their entire steam cloud to get back to a stable state).

@Darrell: I encountered a similar problem when I was testing out the CMYK jpgs. No need to wipe the whole cloud though, one can manage their TTS cloud and delete any crash-causing files through https://github.com/leberechtreinhold/tts-cloud-manager

@Dmitriy L thanks, will keep this in mind if it happens again

My bug was merged to this one (suggestion, if ya’ll merge a post someone makes either leave it there so it redirects to where its being moved or send a notification. I had to manually search for my post to figure out what happened to it.)

Anyway,

I followed the steps on github, but they are flawed.
First the instructions say to go to release and download the zip file (which I did, but it should be specified which of the two zip files).
The zip file does not have an executable, so, I downloaded the executable and placed it in a folder on my desktop (along with the files that were inside the zip).
I ran the executable and windows 10 tried to block it as a potential harmful file. I told it to run it anyways. Nothing happened.
I ran it as an administrator and nothing happened.
I disabled my antivirus and nothing happened.
I ran compatability mode troubleshooter and tried all settings possible. Nothing happened.

If anyone has this issue, you need to look into all releases and download the one that says v1 (and then download the ones that say 0.2 and replace the files found in the v1 folder?). That’s how it worked for me. Maybe you just need v1.