Search Issue Tracker

In Progress

Fixed in 6000.0.0f1

Fix In Review for 2022.3.X

Votes

2

Found in

2021.3.36f1

2022.3.22f1

6000.0.0b13

7000.0.0a1

Issue ID

UUM-68288

Regression

Yes

Crash on RevealInFinder when building a project in headless mode

--

-

Reproduction steps:
1. Setup a headless Windows machine
2. Setup the “repro” project
3. Run the Editor with: "C:\Program Files\Unity\Hub\Editor\<version>\Editor\Unity.exe" -batchmode -buildTarget StandaloneWindows64 -quit -projectPath </path/to/repro/project> -executeMethod BuildScript.BuildWindows

Expected results: Project is built
Actual results: Unity Editor crashes

Reproducible with: 2021.3.27f1, 2021.3.34f1, 2022.3.21f1
Not reproducible with: 2021.3.24f1

Reproduced on: Windows 10
Not reproduced on: No other environment tested

First lines of the stack trace from crash.dmp:
Unity.exe!RevealInFinder(struct dynamic_array<class core::basic_string<char,class core::StringStorageDefault<char> >,0> const &) Unknown
Unity.exe!RevealInFinder(class core::basic_string_ref<char>) Unknown
Unity.exe!EditorUtility_CUSTOM_RevealInFinder(class ScriptingBackendNativeStringPtrOpaque *) Unknown
mono-2.0-bdwgc.dll!00007ff977434b6e() Unknown
mono-2.0-bdwgc.dll!00007ff97736d204() Unknown

Notes:

* CQA did not reproduce this issue, as we didn’t set up a headless machine for this bug report
* All the bug information was provided by the bug reporters
* As per the bug reporter, this issue didn’t happen in 2021.3.24f1, so a regression happened somewhere between it and 2021.3.27f1

  1. Resolution Note (fix version 6000.0.0f1):

    Fixed so that Finder/Explorer will no longer open in batch mode. Please ensure that -batchmode is provided on the command line when running batch mode, especially on headless systems.

Comments (1)

  1. redwyre

    Mar 31, 2024 14:16

    I assumed my case was caused by other environment changes at the same time, but I did upgrade from 2022.3.11 to 2022.3.21 if that helps narrow it down

    Also the title says headless but from what I've read "-batchmode" doesn't assume headless and only suppress windows that require _interaction_, but when Unity is running in a service context (on windows) the OS is going to block some more stuff.

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.