Search Issue Tracker

Fixed in 2018.3

Fixed in 2019.1



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 (142)

  1. Ffbed214ed2c3a124dcd4811eb0f99f9?d=mm


    Jan 17, 2019 22:12

    Still occuring in 2018.3.2f1 unfortunately. Expected as the release notes didn't suggest otherwise though.

  2. Ced9fac7af09d8933b3f06d8d5111426?d=mm


    Jan 17, 2019 19:30

    has anyone tested on 2018.3.2 ?
    I'm using 2018.3.1f1 and really hoping for a fix soon.

  3. 4103a22c52b0d724829bb03fa307b56b?d=mm


    Jan 17, 2019 18:48

    @ApeSoup: Well, that's disappointing. Thank you for verifying that.

    @RichardKettlewell: Is there an estimate on when this issue might be fixed? I was hopeful we might see it patched in 2018.3.2, and while that build has a lot of good fixes in it, I don't see VR bugs mentioned anywhere.

  4. B181d45c4808017ecd804d852fa5472b?d=mm


    Jan 17, 2019 15:07

    One of the reasons I wish unity was open source is because this would be posted as an issueo on GitHub and we all could have helped find a temporary solution while waiting for the official one. Sucks this one does under the radar for 2 months. Glad to hear the fix is under way.:D

  5. 3747c31b3b679fbfaf1d157286bfa431?d=mm


    Jan 16, 2019 23:48

    Good to see that this is being investigated.

  6. 6238000e7287865590cd725aa1be71da?d=mm


    Jan 16, 2019 17:22

    Just wanted to make sure to say that I'm not using VR at all and this happens with many particle effects from the Asset Store.

    Running 2018.3.0f2

  7. 95cfe7fd4e884b0551712b76f8de72be?d=mm


    Jan 16, 2019 16:42

    We have an extremely simple repro case for this. VR project with 40 instances of a looping particle system using a billboard renderer. Open profiler and select profile editor.
    Run for 30 seconds and observe that the memory is relatively stable. When stopping play, the editor hangs for a few seconds and then memory usage jumps up by about 10 GB in the profiler and does not go back down.

  8. Ffff6d6f1bcc2a29473e5f3fbeb2ea11?d=mm


    Jan 16, 2019 16:40

    Hey all, this may get lost in the sea of comments pretty fast, but I want to post an update to say that we are working on this issue right now as a priority.

    I will also try to find out why we have failed to get the necessary eyes on this bug sooner than the 2 months it has taken, so we can do better in the future.

  9. Eedf8eed6015e1c3ed12c75bad501b17?d=mm


    Jan 16, 2019 08:48

    No - upgrading to dx12 does not resolve the issue - it just takes a while before it shows

  10. 4103a22c52b0d724829bb03fa307b56b?d=mm


    Jan 15, 2019 18:09

    The memory leaks are especially intense for particles that use mesh renderers (up to 100 MB per particle system in our test). This can easily cause the application to try to allocate more memory than is available and crash the user's PC.

    Note that these memory leaks appear specific to DX11. Upgrading our project to DX12 appears to have eliminated the leaks, although we'll have to test more to be sure.

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.