Search Issue Tracker

Fixed in 2018.3.X

Fixed in 2019.1.X



Found in





Issue ID




[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

- Is known to also cause memory leaks

  1. Response avatar

    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.

Comments (144)

  1. 3747c31b3b679fbfaf1d157286bfa431?d=mm


    Jan 11, 2019 08:04

    Really hope this gets fixed soon.

  2. 3747c31b3b679fbfaf1d157286bfa431?d=mm


    Jan 11, 2019 08:01

    Really hope this gets fixed soon.

  3. B3c61178441bca1c6e7903932374f52a?d=mm


    Jan 10, 2019 03:48

    +1 Happens on 2018.3.0f2 ... Started happening after upgrading from 2018.3.0b6
    > Only happens when using a HMD. If running without a HMD it doesn't occur.
    > Doesn't happen the first time I press play after opening Unity, but will happen every time after the first time.
    > Seems to be also causing memory leeks. It will sometimes stop climbing by it's self, also seems to stop climbing if you pause the game, sometimes it doesn't stop climbing and my PC runs out of memory and shuts down immediately. The only way I've found to get back the runaway memory is to restart Unity.
    > Looking at the Unity profiler the memory leeks appears within the GfxDriver (I've seen this up to 26.27 GB!)

  4. 995e9653cd99d97124d5963ae6101166?d=mm


    Jan 10, 2019 01:06

    .. still an issue i see :/

  5. Ddd9b7fb724f92a176b14e38b0f2a701?d=mm


    Jan 09, 2019 21:41

    Another issue that I found is that after exiting play mode, the whole scene view is lagging extremely hard. Profiler shows around 100ms per frame for Gfx.WaitForPresent(). When I exit play mode without using VR (using the VR Rig simulator from VRTK) I do not have this issue and the error TASK.RASTERDATA.INDEXBUFFER == NULL does not occur.

  6. 4fb89418e19b1e8e126a6bae9c803399?d=mm


    Jan 08, 2019 23:55

    Yeah getting the same issue. First, I thought its SteamVr but now I can see its Unity 2018.3.0 with the particle system

  7. B181d45c4808017ecd804d852fa5472b?d=mm


    Jan 08, 2019 05:19

    Any status on a fix? Is it still being investigated or has the underlying issue been found? Is a fix underway?

  8. Cf1cb731da8d80054fc85b09be545aad?d=mm


    Jan 08, 2019 03:16

    Does anyone know how, if possible, to downgrade to Unity 2018.2? It crashes every time I try.

  9. 942485618cd561e7cce75bfa7c526296?d=mm


    Jan 08, 2019 01:06

    +1. As soon as I upgraded to 2018.3.0f2 my particle systems that worked fine started spitting out this error.

  10. Cf1cb731da8d80054fc85b09be545aad?d=mm


    Jan 08, 2019 00:37

    I also really need a fix asap. I've been working in 2018.3 since it came out and can't revert to 2018.2. So I'm stuck. My game is full of particle effects so this is a really bad bug for me

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.