Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
2017.2.0b3
Issue ID
934783
Regression
Yes
[UWP] Debugger works incorrectly in certain scenarios
Reproduction steps:
1. Build the the attached project to UWP with C# projects enabled
2. Put a breakpoint on Line 9 and Line 10
3. Start debugging the project
4. Breakpoint on Line 9 will be hit
5. Continue debugging (by pressing F5 or F10)
5. Breakpoint on Line 10 will not be hit
Reproduction gif: https://gyazo.com/468a1988889e97a010f083ca69796a0b
Regression introduced in 2017.2.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment