Search Issue Tracker
Fixed in 2019.1
Fixed in 2019.1
Votes
1
Found in
2019.1.0a13
2019.1.0b1
2019.2.0a1
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
- [IL2CPP][Android] Incorrect symbol length/symbols returned with "AndroidJavaClass"and "AndroidJavaProxy" on Android < 5.1.1
- Animating the alpha channel of a color in a material causes the RGB channels to be reset to 0
- [Mobile] TouchScreenKeyboardType is missing DecimalPad
- Memory leak in Scene Memory/RenderTexture when Scene View is active and 'Animated Materials' + 'Post Processings' toggles are on
- Ctrl + F should start search in PackageManager
Add comment