Search Issue Tracker

Active

Votes

0

Found in

6000.0.58f1

6000.2.7f1

6000.3.0b6

6000.4.0a2

Issue ID

UUM-123222

Regression

No

Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions

-

A crash has been observed in the Editor affecting various workflows. These crashes have been reported to happen when:
- Entering Play mode
- Attaching the debugger to Visual Studio
- Placing a breakpoint
- Connecting to a server via 3rd party package
- Sending packets via 3rd party package

Reproducible with: 6000.0.51f1, 6000.0.58f1, 6000.2.0b4 - 6000.2.7f2, 6000.3.0b1 - 6000.3.0b6, 6000.4.0a2

Reproduced on: Windows 10, Windows 11 (reported machines)
Not reproduced on: No other tracked environments

Note:
- Not reproduced by CQA
- Many users report having/using various 3rd party packages at the time of the crash

First few lines of the stack trace:
6 0x00007FF96FC8B2D4 (Unity) scripting_method_invoke
7 0x00007FF96FC631E3 (Unity) ScriptingInvocation::Invoke
8 0x00007FF96FC4E604 (Unity) MonoBehaviour::CallMethodIfAvailable
9 0x00007FF96FC4E732 (Unity) MonoBehaviour::CallUpdateMethod
10 0x00007FF96F67392C (Unity) BaseBehaviourManager::CommonUpdate<BehaviourManager>
11 0x00007FFCA95DC5CA (Unity) BehaviourManager::Update

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.