Search Issue Tracker
In Progress
Under Consideration for 6000.0.X
Fixed in 6000.3.4f1, 6000.4.0a1
In Progress in 6000.3.X
Votes
1
Found in
6000.0.55f1
6000.2.2f1
6000.3.0a6
Issue ID
UUM-115382
Regression
No
Unity Player crashes on (UnityPlayer) UnityMain and an Access Violation reading location error in ParticleSystem::Emit occurs when running Player with -debugallocator and using Particle Systems with a complex hierarchical structure
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open Build Profiles (File > Build Profiles)
3. Select “Development Build”
4. Click “Build“
5. Open Windows' Command Prompt
6. Navigate to the build’s location in Command Prompt
7. Enter “EmptyURP.exe -debugallocator”
Expected result: The Particle System subemitters continue to emit, and the Player does not crash
Actual result: Player crashes
Reproducible with: 6000.0.55f1, 6000.2.2f1, 6000.3.0a6
Reproducible on:
Windows Standalone Player
Not reproducible on:
Play Mode
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
First few lines of Stacktrace:
0x00007FFE2A260F76 (UnityPlayer) UnityMain
0x00007FFE2A23DDE3 (UnityPlayer) UnityMain
0x00007FFE2A218C1B (UnityPlayer) UnityMain
0x00007FFE2A26CB50 (UnityPlayer) UnityMain
0x00007FFE2A2615B4 (UnityPlayer) UnityMain
Note:
- When the Visual Studio debugger is attached, an Access Violation reading location error in ParticleSystem::Emit occurs
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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
- [Linux] Bug Reporter window is in Light mode when the Editor theme is Dark mode
Resolution Note (fix version 6000.4.0a1):
Fixed in 6000.4.0a1