Search Issue Tracker
Fixed
Fixed in 2020.3.43f1, 2021.3.16f1, 2022.2.3f1, 2023.1.0a21
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.14f1
2022.2.0b5
2023.1.0a8
Issue ID
UUM-12672
Regression
No
Multithreaded builds sometimes don't print the stack trace when using IL2CPP Scripting Backend
Reproduction steps:
1. Open the attached project “PlayerLogBugUnity_1316147.zip“
2. Build And Run the project using IL2CPP Scripting Backend
3. In the built project press the “Thread Test” button
4. Open the Player.log file(<AppData>\LocalLow\Harebrained Schemes\PlayerLogBug\)
5. Look for log lines with no call stack
Expected result: Every log line has a call stack
Actual result: Some log lines do not print the call stack, instead they print “{{WriteLogs_Thread4 - LogMessage[0] - logMethodID[0] A simple log message that's kind of long. I'm not sure if long messages are...}}“
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0b5, 2023.1.0a8
Reproduced on: Windows 10 Pro
Notes:
1. Reproduced on only modern machines (example: 11th Gen Intel(R) Core(TM) i9-11900H @ 2.50GHz, 2496 Mhz, 8 Core(s), 16 Logical Processor(s))
2. Not reproduced on a laptop with a i9-9880H CPU @ 2.30GHz, 2304 Mhz, 8 Core(s), 16 Logical Processor(s)
3. Does not reproduce when using Mono Scripting Backend
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2023.1.0a21):
Fixed in: 2023.1.0a21