Search Issue Tracker
Fixed in 2021.2.X
Votes
12
Found in
2018.4
2019.3.15f1
2020.2
Issue ID
1258244
Regression
No
"PlayerLoop internal function has been called recursively" error is thrown when calling NewScene() from the Update function
How to reproduce:
1. Open user-submitted project (PlayerLoopRecursively.zip)
2. Open the SampleScene
Expected result: no errors are thrown
Actual result: "PlayerLoop internal function has been called recursively" error is thrown
Reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a15
Notes:
Full error - An abnormal situation has occurred: the PlayerLoop internal function has been called recursively. Please contact Customer Support with a sample project so that we can reproduce the problem and troubleshoot it.
UnityEditor.SceneManagement.EditorSceneManager:NewScene (UnityEditor.SceneManagement.NewSceneSetup,UnityEditor.SceneManagement.NewSceneMode)
ProblematicScript:Update () (at Assets/ProblematicScript.cs:18)
-
johanhelsing_attensi
Dec 10, 2020 09:21
I have customers reporting this in 2019.4.10, with chrome 87 (not edge though).
Can't reproduce on my machine, though.
-
fatboynotslim
Oct 26, 2020 01:02
I just got this in 2019.4.11f1
I was in a development build, with the console showing some errors.
I clicked on one of the console buttons and got this error multiple times.
-
Braza
Jul 05, 2020 19:18
I face this issue with recent 2019.4.1f1
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
- "Shader warning in 'Hidden/HDRP/DownsampleDepth'" warnings are thrown after building a project
- Scene is not rendered and appears black when the Custom Renderer Feature is utilized
- [ShortcutManager] The Context Menu is not updated in the Shortcuts menu when resolving a Binding Conflict
- [Quest] Foveation Level is 0 when SRP Foveation is enabled
- Freeze when displaying text with "-T" in Play mode
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a16