2019.3 Assertion failed on expression: 'task.rasterData.vertexBuffer == NULL'

Hi there, after a recent upgrade from 2019.2 to 2019.3 I get an error while playing the game:

UnityEngine.GUIUtility.ProcessEvent(Int32, IntPtr)

Leaving the game idle generates the error at random rate, once after 1 minute, once after 5 minutes… I can’t find any pattern. I noticed that removing some particle effects causes the error to appear less often, but I can’t find any particular object responsile for it, nor reproduce it in a new scene.

How do you think should I proceed to find out the reason for the error? Any help or tip would be most appreciated.

3 Likes

Yeah same issue here, but not only with Particle Effects i also get the same Error with LineRenderer and TrailRenderer.
At least i found the Objects responsible for the Error. Turning them off solved the Error.

1 Like

Same with me, not sure what is causing the issue. I seem to get the “task.rasterData.vertexBuffer == NULL” intermittently in editor mode. This usually results in a crash shortly afterwards.
I started seeing this issue after upgrading to 2019.3.0f5, and it is still happening on 2019.3.0f6

In my project, it seems like its the line renderers. I’m not noticing any actual issues so I’m just going to ignore the errors and hope they get patched soon…

1 Like

I do not use line renderers, so this is not my case.

I noticed that the error disappears after switching to experimental directx 12 API (project settings → player → other settings → auto graphics api for windows off → + direct3D12 (experimental)). This suggest there is maybe something wrong with 2019.3 (I’m currently running 2019.3.0f6). This case was also discussed in 2018.3.0f2 - Assertion failed on expression and computer crash - Unity Engine - Unity Discussions

Maybe it has something to do with urp/gi/2d renderers… Nevertheless, I can’t find any confirmation - is it a bug, is it going to get fixed?

2 Likes

I upgraded to 2019.3 to see if the decal projectors were working in shadowed areas again.

On 2019.3, on d3D11, I have this issue when I’m using a line renderer. Things in play mode sometimes don’t work while the errors show up, so I tried switching to Vulkan (still on 2019.3).

On Vulkan, this issue went away, but then the editor randomly… CPU usage spikes and the interface becomes unusably slow, eg, 10 seconds to open a menu etc. Seems to happen mostly after entering or exiting play mode.

Switched yet again to d3D12. It costs me about 20-40 fps to use it, but its the only way I’ve been able to get stability back. Its an incredible performance hit though.

Also getting this error. I’ve used 2019.2.1f1 all the way up to 2019.2.19f1 without ever seeing it, but as of upgrading to 2019.3.0f6 today, I see it regularly. Unfortunately still unsure why or when exactly…

Did someone report it?

I’m also getting this error when using the particle system in 2019.3.0f6 with the Universal Rendering Pipeline. I’m using both a trail renderer and a particle system - I had the trail renderer going first with no problems, then the error started showing up when I added a particle system. I submitted a bug with a sample project.

1 Like

Exactly the same situation here.

I have upgrade today from 2019.2 to 2019.3 and I have the same problem in every porject.

1 Like

I tested this. I am getting this error for Smoke particle effects and Line renderer too.

Still happening with 2019.3.1f1.

Same thing here, happens a lot, hard to post a bug report though, it seems so random in the way it happens.

It is definitely linked to particle system in my case.

2 Likes

Same here

Same. Rolling back to 2019.3.0b11

I also get this with line renderer, but haven’t looked at it in more detail yet. Is there a bug logged for this yet?

Also getting this error. Turning off particles fixes it for me. Running 2019.3.0f6

2 Likes

Can anyone at Unity indicate if this is an issue we should be concerned about?

Happening to me as well, it’s definitely a line renderer’s cause there…