How to reproduce:
1. Open the attached “IN-101185” project
2. Open the “SampleScene”
3. Search for the “Unsafe.Burst.ActivationTestModule” script in the Project window open it
4. Place a breakpoint on line 86 and attach the script to Unity
5. Return to the Editor and select “Enable debugging for this session” in the pop-up window
6. In the Hierarchy, unfold GameObjects “Test Object Parent” and “Burst Data Model Tests” and select “Phase Two”
7. In the Inspector, right click the “Unsafe Network Activation Test Module (Script)” Component and click “Test Fire Network”
8. Observe the result
9. Open your IDE, un-attach, then re-attach the script to the Editor
10. Select the “Phase Two” GameObject in the Hierarchy and repeat step 7
11. Observe the result
Expected result: The breakpoint is consistently hit
Actual result: The behavior is inconsistent; different behaviors can occur each time (see notes)
Reproducible with: 1.8.18 (2022.2.14f1), 1.8.24 (2022.2.14f1, 2022.3.66f1, 6000.0.57f1, 6000.2.4f1, 6000.3.0b1)
Couldn’t test with: 1.8.17 ((2022.2.14f1) Could not solve error “'Unsafe' is inaccessible due to its protection level”) 1.8.24 (2022.2.13f1 (5f5de2657605) Could not solve issues with Collections package from downgrading))
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- Observed behaviors:
- Numbers are printed to the Console
- The Editor gets stuck on “Menu.Test Fire Network”
- The IDE window becomes focused
- Reproduces with Visual Studio 2022 and Rider 2025.1.2. No other IDE tested