Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
224
Found in
2018.3.0b8
2018.3.0b9
2018.3.0b10
2019.1.0a9
Issue ID
1099125
Regression
Yes
[VR] Particle Systems cause "task.rasterData.indexBuffer == NULL" error and lead to graphical glitches
Steps to reproduce:
1. Create a new project
2. Enable VR
3. Create a particle system
4. Enter playmode and put it in your HMDs view
5. If error doesn't show, repeat Stop / Play of playmode again. (when doing this i can repro it with the MockHMD)
Result: "task.rasterData.indexBuffer == NULL" error in the console and potential graphical glitches
Reproduced on 2018.3.0b8, 2018.3.0b10, 2019.1.0a9
Not reproduced on 2018.2.16f1, 2018.3.0a1, 2018.3.0b7
Regression introduced in 2018.3.0b8
notes:
- Is known to also cause memory leaks
Comments (145)
-
RWeijermars
Jan 06, 2019 11:00
Hi everyone, has anyone perhaps found a workaround yet. Other than disabling particles ;)? And Unity gods, any news on the fix?
Kind regards,
Ray -
RWeijermars
Jan 05, 2019 22:57
I’ve encountered this bug too in Under a Desert Sun VR. This really needs a fix. Hope the vote helps
-
ErThu
Jan 04, 2019 18:59
+1 needs to be fixed asap. Every particle system causes huge memory leaks which means to either disabling them all or restart unity after a few tests in play mode
-
chatrat12
Jan 04, 2019 13:42
Pretty bummed this bug made it out of beta. My project already relies on nested prefabs and I can't downgrade. Wish this had higher priority :O
-
chatrat12
Jan 04, 2019 13:42
Pretty bummed this bug made it out of beta. My project already relies on nested prefabs and I can't downgrade. Wish this had higher priority :O
-
RSmart
Jan 04, 2019 01:32
+1 Please fix this.
-
Jaquest
Dec 29, 2018 12:06
+1 with Unity 2018.3.0f2
Disabling particle systems -> no errors.
Enabling particle system -> errors. -
wagaga
Dec 26, 2018 10:02
Unity2018.3 has this problem, and the memory will continue to increase, leading to crash.
Please fixed! -
wagaga
Dec 26, 2018 10:01
Unity2018.3 has this problem, and the memory will continue to increase, leading to crash.
Please fixed! -
GiedriusUnity
Dec 20, 2018 13:24
The issue is currently being investigated by a developer, we are working to resolve it as soon as possible
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
- Render Graph Execution errors when using GPU occlusion culling with 'Opaque Objects' frame setting disabled on a Camera
- Animator window: “Delete” menu item not greyed out for Base Layer context menu
- Resetting “PC_RP Asset (Universal Render Pipeline Asset)” causes Game view to become black and throws Renderer and NullReference errors in the Console window
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
Resolution Note (fix version 2018.3):
The fix has now landed in our various release versions. 2019.2.0a4, 2019.1.0b2 (available approx 1st February), 2018.3.5f1 (available approx 6th February). Thank you for your patience.