Search Issue Tracker
Duplicate
Votes
0
Found in
2022.2.0a3
2022.2.0a4
Issue ID
1408068
Regression
Yes
Profiler (Standalone Process) crash on StopAssetImportingV2Internal when opening and upgrading the Materials
Reproduction steps:
1. Create a new URP project
2. Open Window -> Analysis -> Profiler (Standalone Process)
3. Press "Ok" in the opened up "Profiler (Standalone Process)" window
4. Press "Ok" in the "URP Material upgrade" window
Expected result: Profiler launches successfully
Actual result: Profiler crashes
Reproducible with: 2022.2.0a3, 2022.2.0a7 (14.0.0)
Not reproducible with: 2020.3.30f1 (10.8.1), 2021.2.14f1 (12.1.5), 2022.1.0b10 (13.1.6), 2022.2.0a2 (13.1.7)
Could not test with: 2019.4.36f1 (No Standalone Process Profiler)
Note:
- reproducible with HDRP as well
First lines of stacktrace:
0x00007ff722fd75d3 (Unity) StopAssetImportingV2Internal
0x00007ff7211b2bd8 (Unity) AssetDatabase_CUSTOM_StopAssetEditing
0x0000021b0e253d77 (Mono JIT Code) (wrapper managed-to-native) UnityEditor.AssetDatabase:StopAssetEditing ()
0x0000021b0e253ad3 (Mono JIT Code) [MaterialPostprocessor.cs:54] UnityEditor.Rendering.Universal.MaterialReimporter:ReimportAllMaterials ()
0x0000021b0e251f13 (Mono JIT Code) [MaterialPostprocessor.cs:94] UnityEditor.Rendering.Universal.MaterialReimporter/<>c:<RegisterUpgraderReimport>b__2_0 ()
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #1399870