Search Issue Tracker

Fixed

Fixed in 2022.3.61f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7

Votes

1

Found in

2022.3.59f1

6000.0.32f1

6000.1.0b8

6000.2.0a4

Issue ID

UUM-98081

Regression

Yes

Crash on invalid_parameter_internal when starting Standalone Profiler

-

How to reproduce:
1. Open the attached “IN-92300.zip” project
2. Open the “SampleScene”
3. Open the Standalone Profiler from Window>Analysis>Profiler (Standalone Process)
4. Observe the crash

Reproducible in: 6000.0.32f1
Not reproducible in: 2022.3.20f1

Reproducible on: Windows 11
Not reproducible on: No other environments tested

First few lines of stacktrace:

{noformat}0x00007ffb92bf76ed (Unity) StackWalker::ShowCallstack
0x00007ffb92c076a9 (Unity) PlatformStacktrace::GetStacktrace
0x00007ffb93e716ee (Unity) Stacktrace::GetStacktrace
0x00007ffb9323769b (Unity) winutils::PrintStackTrace
0x00007ffb932365e1 (Unity) winutils::CrashHandler::DefaultInvalidParameterHandler
0x00007ffb955a45e9 (Unity) invalid_parameter_internal
0x00007ffb955a453e (Unity) invalid_parameter
0x00007ffb955a4671 (Unity) invalid_parameter_noinfo
0x00007ffb955b5b72 (Unity) _stdio_common_vsscanf
0x00007ffb923cecc9 (Unity) sscanf{noformat}

Note: The crash was not reproduced by CQA

  1. Resolution Note:

    postponing U7 port.

Add comment

Log in to post comment