Search Issue Tracker

Fixed in Unity 2019.1

Votes

1

Found in

2019.1.0b1

Issue ID

1122909

Regression

Yes

Editor/Player crashes when the logfile path contains non-ASCII characters

Editor - Other

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 1Crash, freeze, data loss, work stops

How to reproduce:
1. Create a shortcut for Unity Editor
2. Add a -logfile command line argument followed by a path, containing non-ASCII characters
3. Launch Unity via this shortcut

Expected result: Unity launches without any issues
Actual result: Unity crashes and is re-launched again

Reproducible with: 2019.1.0a13, 2019.1.0b2, 2019.2.0a4
Not reproducible with: 2017.4.20f1, 2018.3.5f1

Notes:
Once Unity re-launches itself a log will not be generated at the custom path
Also affects built player shortcuts

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.