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
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.
Latest issues
- Memory leaks and Editor crashes/freezes when using decimal values in Gizmos
- "The page you were looking for doesn't exist" message appears when trying to Sign in using Unity Hub/Editor
- [Regression] Enviroment lighting is broken in the 2017.4.27f1 version
- Usymtool does not support arm64e
- [Addressables] Exception is thrown when accessing AssetReference.Asset before the asset is loaded
Add comment