I was updating some asset when I got the regular "Image Resized" message - I've never tired opening the logs before but this time since I have a low of updates I wanted to see if there were any details and I got a strange message written in Mandarin.
This is on the version 4.2.42
The message looks AI generated - apparent from the repeating sentences. I'm not sure what's supposed to be here exactly because it's the first time I opened this log but I'm sure it's not supposed to be this 
It seems like you're encountering an issue with the log file displaying unexpected content in Mandarin, which appears to be AI-generated or repetitive. This could be due to a glitch or corruption in the log file. To resolve this, you might want to try restarting Spine and checking if the issue persists. If the problem continues, you could consider deleting the existing log file to allow Spine to generate a new one. The log file can typically be found by following the instructions on the Spine troubleshooting page.
I have just tried restarting my Spine and the issue persists but I get a slightly different message.
Please attach the plain file here. The fancy new Notepad has Copilot, which is likely messing with the display of the file somehow.
I unfortunately did not save the file, but after reopening Spine the next day, I find I cannot repeat this error. It would only make sense Copilot is the cause but I've got no idea why it would have done so - new experimental features I guess 
.
Thanks for replying tho Mario !
Hi I'd like to update this bug report with the same error now when trying to Open Log from an Export Warning.
Text as written is (I've also attached the file itself):
灓湩慌湵档牥㐠㈮〮സ䔊潳整楲潓瑦慷敲䰠䍌⠠⥃㈠ⴳ〲㐲簠栠瑴㩰⼯獥瑯牥捩潳瑦慷敲挮浯楗摮睯〱䠠浯楓杮敬䰠湡畧条浡㙤‴〱〮潆睲牡敤潴攠楸瑳湩灓湩湩瑳湡散മ
圀剁䥎䝎›敍桳椠慭敧映汩楤敭獮潩獮挠慨杮摥›㩃ぜ弱祍䘠汩獥䝜浡䍥慨杮牥匠畴楤屯㔱䐠祡屳湁浩瑡潩屮桃牡捡整獲䑜睥屩灓湩彥捓湡楮杮嘠桥捩敬楜慭敧屳瑓湡層瑓浯捡湰൧䤊慭敧映牯愠瑴捡浨湥⁴牛来潩㩮匠慴摮䐯睥彩潂瑯彨摉敬歳汥瑥湯›敄楷捓湡楮杮汳瑯›敒敦敲据嵥渠瑯映畯摮›瑓湡⽤敄楷䉟潯桴䥟汤䤊慭敧映牯愠瑴捡浨湥⁴牛来潩㩮匠慴摮䐯睥彩潂瑯彨瑓湡楤杮歳汥瑥湯›敄楷捓湡楮杮汳瑯›敒敦敲据嵥渠瑯映畯摮›瑓湡⽤敄楷䉟潯桴卟慴摮湩൧䤊慭敧映牯愠瑴捡浨湥⁴牛来潩㩮匠慴摮䘯捡彥摉敬歳汥瑥湯›敄楷捓湡楮杮汳瑯›慆散䥟汤嵥渠瑯映畯摮›瑓湡⽤慆散䥟汤䤊慭敧映牯愠瑴捡浨湥⁴牛来潩㩮匠慴摮䐯睥彩潂瑯彨摉敬歳汥瑥湯›敄楷捓湡楮杮汳瑯›敒敦敲据嵥渠瑯映畯摮›瑓湡⽤敄楷䉟潯桴䥟汤䤊慭敧映牯愠瑴捡浨湥⁴牛来潩㩮匠慴摮䐯睥彩潂瑯彨瑓湡楤杮歳汥瑥湯›敄楷捓湡楮杮汳瑯›敒敦敲据嵥渠瑯映畯摮›瑓湡⽤敄楷䉟潯桴卟慴摮湩൧䤊慭敧映牯愠瑴捡浨湥⁴牛来潩㩮匠慴摮䘯捡彥摉敬歳汥瑥湯›敄楷捓湡楮杮汳瑯›慆散䥟汤嵥渠瑯映畯摮›瑓湡⽤慆散䥟汤
KrushZilla Hmm, I tried simply correcting the encoding to fix the garbled characters, but it didn't work. Would it be possible to provide the Spine project that reproduces the problem via email?: contact@esotericsoftware.com
Please include the URL of this forum thread in the email so we know the context. Then we can take a look at what's wrong.
KrushZilla Thank you for providing the Spine project files! I exported them in JSON format and checked them, but I could not reproduce the character encoding issue. Therefore, I believe there is a problem with your computer settings.
Here is the log I obtained for your reference:
Spine Launcher 4.3.01 (macOS Apple Silicon)
Esoteric Software LLC (C) 2013-2025 | http://esotericsoftware.com
Mac OS X aarch64 15.3.1
Apple, Apple M1, 2.1 Metal - 89.3
Starting: Spine 4.2.43 Professional
Spine 4.2.43 Professional
Licensed to: ****** ****** <***********************>
Started.
Update available: 4.3.36-beta
OpenAL 1.1, Default audio device
Image for attachment [region: ************* skeleton: *************, slot: *************] not found: *************It may be a good idea to try opening the spine.log file in a different way to see if the correct log is displayed.
Misaki Hi, since encountering this error the first time almost 3 weeks ago. The issue is inconsistent, after a computer restart the issue does goes away. It's not the biggest bother I just thought I'd report it since it was very strange. It could be my computer specific thing, it's definitely an AI generated message possibly written by Copilot but I'm not sure why it would generate itself when trying to create a Spine error log.
Nonetheless, thanks for the help! 
KrushZilla It's always helpful when you report issues you've noticed! Other users may have the same problem in the future, and this thread may be helpful to someone else. Thank you for reporting it!
I thought a little more about your issue and realized that yours is just a common encoding issue that is known as mojibake.
I've just copied the text that you pasted in the your message above (#6):
KrushZilla Text as written is (I've also attached the file itself):
灓湩慌湵档牥㐠㈮〮സ䔊潳整楲潓瑦慷敲䰠䍌⠠⥃㈠ⴳ〲㐲簠栠瑴㩰⼯獥瑯牥捩潳瑦慷敲挮浯楗摮睯.....
into vscode with UTF-16 LE encoding.
Then, changed the encoding to UTF-8 and got this result.
I've hidden the text as you did in your image:
but I can easily see the result is the same.
In Spine, when you click the Open log button it just trigget the OS to open the txt file, nothing special. So, the issue is Notepad sometimes interpreting the text content with the wrong encoding.
Which language are you using in your OS?
I've also noticed you have an old launcher (4.2.08). It highly recommended to upgrade it. You can do that downloading the latest launcher from your license page.
Davide I have just downloaded the latest launcher so hopefully that fixes it. I'm not really sure how to check the language I'm using in my OS, but I'll give it a shot looking to solve this encoding issue.
Thanks Davide for the sprinkle of knowledge, never woulda known about encoding or mojibake before 
The real mystery is why your log file has the two unknown characters at the beginning:
Those characters are known to be Byte-order marks (BOM) and in this case are FF FE (in hex) suggesting the text editor use the UTF-16 (LE) encoding (read more about it here).
We currently don't write any BOM, so that's the real mystery. I'm wondering if with the latest notepad version, it sometimes adds BOM by itself.
Did you do anything special with your log file?
Davide Not particularly, I opened the file and saved it to my desktop then immediately uploaded it to the email I sent. I don't think anything there would be considered 'special' haha
Thanks for the information. If it happens again in the future and you notice a pattern that might trigger the issue, please let us know so we can look into it and consider whether there's something we can do to prevent it from recurring
If you opened the file and saved it with the text editor, that could explain how the BOM got added. If you don't re-save it with a text editor, the file Spine writes shouldn't have a BOM.
