Search Issue Tracker
Fixed
Fixed in 6000.4.0b11, 6000.5.0a8, 6000.6.0a1
Votes
0
Found in
6000.4.0b7
6000.5.0a7
6000.6.0a1
Issue ID
UUM-134373
Regression
Yes
Crash on RefreshProfiler::AssetDatabaseProfilerEventCallback during the first import on a new project
How to reproduce:
1. Create and open a new URP project
2. Open the Window → Package Management → Package Manager (not necessary, but sometimes helps to trigger the crash)
3. Wait a few seconds
4. Observe the Editor
Reproducible in: 6000.5.0a4, 6000.5.0a7
Not reproducible in: 6000.0.68f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a3,
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Notes:
- The issue is very inconsistent to reproduce. Therefore, an accurate regression point cannot be confirmed. However, the issue stopped reproducing after testing in 6000.5.0a3, so this is likely where the issue regressed
- Reimporting all the assets does not reproduce the issue
- Sometimes the issue is reproducible multiple times if the crashed project is opened again
- The bug can occur on empty projects as well
- Sometimes the Editor crashes at different times (sometimes straight away, sometimes only after some of the importing has been done), in both scenarios, stack traces are different, but they both end on the same RefreshProfiler::AssetDatabaseProfilerEventCallback call
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.4.0b11, 6000.5.0a8, 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.4.0b11, 6000.5.0a8, 6000.6.0a1
Resolution Note (fix version 6000.5.0a8):
Fixed in 6000.5.0a8
Resolution Note (fix version 6000.4.0b11):
Fix landed