Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2018.1.0f2
Issue ID
1045122
Regression
No
[Player] '(Filename: .../Debug.bindings.h Line: 43)' line is printed in the Player.log with each 'Debug.Log()' call
1. Open the attached "DebugLog.zip" project.
2. Build and run it as standalone.
3. Open the Player.log.
Actual behavior:
- "(Filename: /home/builduser/buildslave/unity/build/Runtime/Export/Debug.bindings.h Line: 43)" is printed after 'test' line.
- This line takes a lot of space in the log when a lot of Debug.Log() calls are made. It doesn't present usefult information.
Expected behavior:
- (Filename: /home/builduser/buildslave/unity/build/Runtime/Export/Debug.bindings.h Line: 43) is not printed.
or
- Simple way to disable logging of this line using Debug.Log().
Reproduced with:
2018.3.0a1, 2018.2.0b8, 2018.1.4f1, 2017.4.5f1, 2017.2.3p1
Windows, macOS
Resolution:
To avoid printing the callstack, you should either turn off the traces by setting the StackTraceLogType to None (see https://docs.unity3d.com/ScriptReference/StackTraceLogType.html) or use Console.WriteLine directly.
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
rohitvishwakarma1819
Sep 25, 2020 13:51
Hey, Did you find the solution ?
Please reply.
Thanks