Search Issue Tracker

Fixed in 2021.2.X



Found in




Issue ID




"PlayerLoop internal function has been called recursively" error is thrown when calling NewScene() from the Update function

Scene Management


How to reproduce:
1. Open user-submitted project (
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

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)

  1. Resolution Note (fix version 2021.2):

    Fixed in 2021.2.0a16

Comments (11)

  1. Alejandro-Beacon

    May 21, 2021 07:51

    Got this on 2020.3.4f1

  2. dansav

    Feb 28, 2021 20:04

    I have the issue with 2019.4.4f1 running WebGL on Firefox

  3. DevPoint_Mark

    Feb 22, 2021 18:56

    I think it is worth to check your other exceptions in editor for example. Because may be your app wont be crashed in editor, but in browser will generate this bug.

  4. DevPoint_Mark

    Feb 22, 2021 17:57

    Reproducing on Unity 2019.4.19f1

  5. DevPoint_Mark

    Feb 22, 2021 17:44

    Reproducing on Unity 2019.4.20f1.

  6. Aoedipus

    Feb 08, 2021 14:26

    Just started getting this with 2020.1.12f1 on startup in WebGl, trying to debug what recent changes may be causing it. Preventing project from loading.

  7. Skade88

    Feb 03, 2021 00:54

    I am seeing this issue in 2019.4.17f1 and 2019.4.19f1. We can reproduce in Chrome 88 on Windows, Ubuntu and MacOS

  8. sgt3v

    Dec 13, 2020 15:43

    Reproducing on Unity 2020.1.17, WebGL Build on IOS 13.4

  9. 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.

  10. 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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.