Search Issue Tracker

Fixed

Fixed in 6000.0.48f1, 6000.1.1f1, 6000.2.0a10

Votes

2

Found in

6000.0.37f1

6000.1.0b5

6000.2.0a1

7000.0.0a20

Issue ID

UUM-97648

Regression

No

Crash on Object::SetCachedScriptingObject when opening the project

-

How to reproduce:
Open the user's attached project

Reproducible with: 6000.0.37f1, 6000.1.0b7, 6000.2.0a4
Could not test with: 2022.3.58f1 (compilation errors in the Console window)

Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested

First few lines of stack trace:
2025-02-13T07:39:10.635Z|0xb4c|0x00007FFDDBF57BB4 (Unity) Object::SetCachedScriptingObject
2025-02-13T07:39:10.730Z|0xb4c|0x00007FFDDBF58D52 (Unity) delete_object_internal
2025-02-13T07:39:10.801Z|0xb4c|0x00007FFDDC30C08E (Unity) CleanupAllObjects
2025-02-13T07:39:10.801Z|0xb4c|0x00007FFDDC30C4CD (Unity) CleanupEngine
2025-02-13T07:39:10.900Z|0xb4c|0x00007FFDDD41C8EA (Unity) Application::CoreShutdown
2025-02-13T07:39:10.922Z|0xb4c|0x00007FFDDD4307AB (Unity) Application::Terminate
2025-02-13T07:39:10.993Z|0xb4c|0x00007FFDDDA56803 (Unity) ContainerPlatform::ContainerWndProc
2025-02-13T07:39:10.997Z|0xb4c|0x00007FFEAE7EEF5C (USER32) CallWindowProcW
2025-02-13T07:39:10.997Z|0xb4c|0x00007FFEAE7EE8CC (USER32) DispatchMessageW
2025-02-13T07:39:10.997Z|0xb4c|0x00007FFEAE8010C3 (USER32) SendMessageTimeoutW

Note: You might need to launch the project several times to crash

Comments (1)

  1. mikeliamschultz

    Feb 28, 2025 03:23

    This crash occurs for me 50% of the time I use the Unity editor. It's having a significant negative impact on my company's ability to hit our deadlines.

Add comment

Log in to post comment