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