Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.24f1
Issue ID
1329615
Regression
No
[macOS] [Linux][2019.4] Stack frames are missing from Console window when in Full Stack trace mode
Reproduction steps:
1. Open project in "1017853.zip" and open SampleScene
2. Open the Console window
3. Clear the console
4. Press on the "burger" button at the top right of the console window
5. In the opened menu go Stack Trace Logging -> All and make sure Full is selected
6. Enter Play Mode
7. Inspect the Console window
Expected result: in the "Invalid AABB inAABB" error message stack frames from Mono are visible (should be ~ 40 frames)
Actual result: stack frames from Mono are not visible (good and bad stack traces in edits) (6 frames)
Reproducible with: 2019.4.0f1, 2019.4.24f1, 2020.2.0a3
Not reproducible with: 2018.4.34f1, 2020.1.0a4 (fix version), 2020.3.5f1, 2021.1.4f1, 2021.2.0a13
Issue is not reproducible on Windows OS
Note: the issue has been fixed in the 2020.1.0a4 trunk
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.4.X):
In 2019 and prior versions, we default script code to "Debug", in later versions the default is "Release" and the issue reproduces. "Release" would need to be used to get full callstacks.