Unity Issue Tracker - [VR] Particle Systems cause "task.rasterData.indexBuffer == NULL" error and lead to graphical glitches

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

XR SDK

Nov 09, 2018

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

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

richardkettlewell

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.
apesoup

Jan 16, 2019 08:48

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

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.
jonagill_rr

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.
jonagill_rr

Jan 15, 2019 18:08

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.
jonagill_rr

Jan 15, 2019 18:08

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.
rmon222

Jan 15, 2019 03:25

This bug also occurs in 2019.1.0a13
dimitris_baud

Jan 15, 2019 00:25

Major blocker for VR development. I need to restart Unity every 3 times I press play.
tatoforever

Jan 14, 2019 23:23

This issue is horrible, I need to revert my project back to 2018.2 and this will take some time.
Not only Unity 2018 is slower than 2017, but 2017 is also slower than Unity 5.6 and 2018.3 is zillions times slower than 2018.2! Every version performance gets affected a lot, what's going on Unity?
Directional shadows suffered a terrible performance bug (I'm seeing 30-40% slower) in 2017 and 2018. Again, whats is going on?
If this keeps going on, I will skip my Pro version till they get fixed. Stop focusing too much on services, your services worth nothing if no one uses your engine at first.
From now, I will skip all 2018 versions till 2018 hit 2018.4 / LTS. See ya in the future.
james_unity988

Jan 13, 2019 21:12

This bug is taking a serious toll on our project development. We are a small indie team and this kind of major bug really harms our opinion of Unity as our game engine of choice. We waited until after the beta to avoid this kind of issue, and there's no workaround. Please, please fix this bug ASAP!!