Search Issue Tracker
Fixed in 2017.2
Votes
0
Found in
5.3.5f1
Issue ID
840149
Regression
No
[WindowsStandalone] Player crash report doesn't consider -logFile argument
How to reproduce:
1. Open the attached project "PlayerCrash.zip"
2. Build test scene (File -> Build Settings -> Build) and name it (e.g. 1.exe)
3. Open cmd
4. Navigate to the folder where is the build
5. Run this command A.exe -logFile xyz.log
6. When player crashes crash dialog appears. It states :The crash report folder named "2016-11-03..." next to game executable
7. Open that crash report folder
8. Notice that crash folder contains only two files(error.log, crash.bin)
or
If one firstly run the game without -logFile argument, it will contain old output_log.txt file
Actual result: crash report uses file "output_log.txt"(if it exists) from the *_Data directory
Expected result: crash report uses file xyz.log as specified on the startup of the game
Reproducible: 5.3.6p8, 5.4.2p3, 5.5.0b10, 5.6.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Vulkan] Crash in Windows Standalone when Vulkan is set as rendering API and player window is out of focus
- "Can't destroy Transform component" Error is thrown when closing a scene that contains a DontSave Prefab with a Child
- [Particle System] Editor freezes when assigning a nested Particle System in the Sub Emitter Module
- Unable to switch to different material when selecting another material from Asset selector window on Particle System Material
- Inspector displaying wrong characters when using ANSI encoding and non latin characters in a Shader property
Add comment