Search Issue Tracker

Fixed in Unity 2018.3

Votes

0

Found in

2018.3.2f1

Issue ID

1119209

Regression

Yes

MissingReferenceException and broken GUI after enter/exit Play mode with Script Execution Order tab open

Scripting

-

-

Priority: 2Necessary for shipping a final release

-

Severity: 3Secondary functionality broken

How to reproduce:
1. Open the attached "Test.zip" project or create a new one
2. In the Menu bar, select "Edit/ Project Settings..."
3. In the Project Settings window, make sure that the "Script Execution Order" tab is selected
4. Enter the Play mode
5. Exit the Play mode
6. Observe the Console window

Expected result: The Console does not contain any errors and Project Settings window is not broken.
Actual result: There are multiple errors in the Console and GUI of the Script Execution Order tab is broken (it is empty, hovering the mouse over it produces even more errors).

Reproducible with - 2018.3.0a4, 2018.3.3f1, 2019.1.0a15, 2019.2.0a2
Not reproducible with - 2017.4.19f1, 2018.3.0a3

Note: The regression was introduced (in 2018.3.0a4) along with the new Project Settings window. (Prior to that, "Script Execution Order" would appear in the Inspector window.)

Errors thrown:
- "MissingReferenceException: The object of type 'MonoScript' has been destroyed but you are still trying to access it. <...>"
- "ArgumentException: GUILayout: Mismatched LayoutGroup.repaint <...>"
- "GUI Error: You are pushing more GUIClips than you are popping. Make sure they are balanced. <...>"
- "Scope was not disposed! You should use the 'using' keyword or manually call Dispose. <...>"

Response avatar

Resolution Note:

Fixed in 2019.2.0a5 Backported to 2018.3.7f1, 2019.1.0b3

Comments (3)

  1. F25db945e005add93f29ca8e53869f17?d=mm

    AmitSuri

    May 21, 2019 22:03

    Yep... Still an issue in Unity 2019.1.3f1

  2. Ee1efe7dc3eb04d507c53a062244219d?d=mm

    firstuser

    May 17, 2019 21:18

    Still an issue in Unity 2019.1.3f1

  3. 7e8acd2a03fc402a1b9b962e4f90dbb7?d=mm

    Aseemy

    Apr 10, 2019 17:37

    Same issue in Unity 2018.3.12f1
    So i guess its not fixed.

All about bugs

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