Search Issue Tracker
Fixed
Fixed in 1.4.6, 1.5.1
Votes
0
Found in [Package]
1.4.5
1.5.1
2.0.1-pre.18
Issue ID
DSTR-1086
Regression
No
Play Mode / Player Test Runner hangs if WaitForSecondsRealtime() is active and the Play Mode / Player is no longer running
Reproduction steps:
1. Open the attached “ReproProject.zip“ project
2. Open the Test Runner window (Window > General > Test Runner)
3. Run the “TestExitPlayModeMidRun“ Test
4. Observe
Expected result: The Test Runner process is stopped if the Play Mode or Player is closed
Actual result: The Test Runner hangs until canceled manually
Reproducible with: 1.4.5 (2022.3.54f1, 6000.0.31f1), 2.0.1-pre.18 (6000.0.31f1)
Reproducible on: M1 Max MacOS 15.1.1
Not reproducible on: No other environment tested
Note: This issue is present in both PlayMode and Player Tests. It only hangs if {{“yield return new WaitForSecondsRealtime();"}} is called when the Play Mode or Player is no longer running.
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note (fix version 1.5.1):
Ensure that an error is raised and the test run is stopped if a PlayMode test method exits PlayMode.
Resolution Note (fix version 1.4.6):
Ensure that an error is raised and the test run is stopped if a PlayMode test method exits PlayMode.