Search Issue Tracker
Double-clicking on "Debug.Log()" message doesn't open the script when Log Stack Trace is set to "Full"
How to reproduce:
1. Open the attached "1308839_Repro.zip" project
2. Open the Scene "SampleScene"
3. Open the Player Settings (Edit->Player Settings...)
4. Make sure in the Other Settings tab under "Stack Trace" Log option is set to "Full"
5. Enter the Play Mode
6. In the Console double-click on the "Hello" message
Expected results: The script is open
Actual results: Nothing happens
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.f1, 2022.1.2f1, 2022.2.0a15
- Installing the Packages on a 3D Template does not reproduce the issue
- The Debug.Log message provides this stacktrace along the log:
0x00007ff7336c8c8c (Unity) StackWalker::GetCurrentCallstack
0x00007ff7336d1069 (Unity) StackWalker::ShowCallstack
0x00007ff734ba564c (Unity) GetStacktrace
0x00007ff735c64803 (Unity) DebugStringToFile
0x00007ff73385c439 (Unity) DebugLogHandler_CUSTOM_Internal_Log
- Upgrading/downgrading the packages that come with Mobile 3D does not produce/fix the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Black screen frame appears in the WebGL Player when the Unity loading screen is over
- Crash on WriteParticleLineVertex when the "Generate Lighting Data" property is enabled in the Particle System
- UI overlay becomes visible in ray-traced reflections when HDR Color output is enabled
- [Mobile] Player silently crashes on a mobile device when using a lot of "Camera" GameObjects (40 and more) in the Scene
- Scene is modified after exiting Play Mode when Graphics Compositor is enabled in HD RP