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
- Particles are respawned when selecting different Particle System child GameObjects
- A gap at the bottom of the screen appears when entering Play mode in full screen
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
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.