Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
1.2.3
Issue ID
VSC-18
Regression
No
Crash on Camera::GetStereoEnabled when inspecting a variable with VSCode debugger
How to reproduce:
1. Open the user’s attached project and scene “MainMenu”
2. Open CharCreationStats.cs in VSCode
3. Place a breakpoint in line 186
4. Attach VSCode debugger to Unity, create a launch.json for Unity Debugger and press “F5”
5. Enter play mode in Editor
6. Press “Pathfinder 2e”, then “+”
7. Enter any board name, then press the button to the right
8. Press the button to the right of the “Players” sub-window
9. Press the bottom right button 3 times
10. Hover on any variable in VSCode
Expected result: VSCode displays the current variable value
Actual result: Unity crashes
Reproducible with: 1.1.4, 1.2.3 (2020.3.5f1, 2021.1.4f1, 2021.2.0a13)
Could not test with: 2018.4.34f1 (project is not starting), 2019.4.24f1 (crashed on play)
Stack trace:
#0 0x0000010a36cae2 in PPtr<RenderTexture>::operator RenderTexture*() const
#1 0x0000010a7e7a3c in Camera::GetStereoEnabled() const
#2 0x0000010a7e83f8 in Camera::GetCameraRect(bool, bool) const
#3 0x0000010a05ec99 in UI::Canvas::GetRenderingDisplaySize()
#4 0x0000010a44754a in Canvas_CUSTOM_get_renderingDisplaySize_Injected(ScriptingBackendNativeObjectPtrOpaque*, Vector2f&)
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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Resolution Note:
There are no fixes planned for this Bug