Search Issue Tracker

Won't Fix

Votes

0

Found in

2022.3.15f1

Issue ID

UUM-57817

Regression

Yes

Crash on UnityEngine.Rendering.RenderPipelineAsset:InternalCreatePipeline () when opening a project

--

-

Reproduction steps:
1. Download, extract, and open the attached “repro-project“
2. Observe the crash

Reproducible with: 2022.3.5f1, 2022.3.15f1
Not reproducible with: 2021.3.33f1, 2022.3.4f1, 2023.2.3f1, 2023.3.0a17

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

First few lines of the stack trace:
0x0000022D7BCEDEB9 (Mono JIT Code) UnityEngine.Rendering.RenderPipelineAsset:InternalCreatePipeline ()
0x0000022D7BCEDA73 (Mono JIT Code) UnityEngine.Rendering.RenderPipelineManager:PrepareRenderPipeline (UnityEngine.Rendering.RenderPipelineAsset)
0x0000022D7BCECE13 (Mono JIT Code) UnityEngine.Rendering.RenderPipelineManager:DoRenderLoop_Internal (UnityEngine.Rendering.RenderPipelineAsset,intptr,UnityEngine.Object,Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle)
0x0000022D7BCED635 (Mono JIT Code) (wrapper runtime-invoke) <Module>:runtime_invoke_void_object_intptr_object_AtomicSafetyHandle (object,intptr,intptr,intptr)
0x00007FF90A084B6E (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\mini-runtime.c:3445] mono_jit_runtime_invoke

  1. Resolution Note:

    We cannot invest in solving this issue. There is several elements here to take into account:
    - The project is huge, it is far from a minimal reproduction project and it would require a lot of time for us to understand what is going on.
    - The project contains a fork of URP certainly with custom modifications. We only support the version we release. If you have an issue with a specific API, please provide us a more precise issue.
    - The implementation of the custom RP don't follow the requirement for it to work. If you look at UniversalRenderPipeline file, it says that it was not filled correctly due to AssetRipper not having some requirement. AssetRipper is developed out of Unity.

    Feel free to submit a shorter project that produce the issue. If possible use non modified render pipeline and no additional tool that generate or modify assets.
    If you want to open your project to get back some content, you can try manually edit the yaml of ProjectSettings/GraphicsSettings.asset:
    - m_CustomRenderPipeline
    - m_SRPDefaultSettings
    This should be what make the editor crash at opening as the serialized layout don't exists anymore due to the modification done on the scrips.

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.