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:

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

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.

 

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.

 

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

 

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 https://forum.unity.com/threads/2018-3-0f2-assertion-failed-on-expression-and-computer-crash.599410

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?

 

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.

 

Exactly the same situation here.

 

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

 

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.

 

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

 

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

 

How did you determine this? That would be great if it's true, as I am in process of moving all of my regular LineRenderer to XRLineRenderer for working in VR, but all other reports including my own seem indicate it's related to particle systems?

p.s. UnityEmployees: Is there a reason that XRLineRenderer is only on github and not available via package manager or built-in directly?

 

Still happening in 2019.3.2f1.

 

I have a similar error and crash in 2019.3.2f1 using particles:
Assertion failed on expression: 'task.computeData.buffer == NULL'

In case someone from Unity reads this, I opened (Case 1221832) with two reproduction projects.

 

Same here with 2019.3.0f6

Seems to be related to trail renderer in my case, and the error log appears only once and seemingly randomly.

 

I found this infobox. but can't hit Apply to Systems

 

Got a link to the case?

 

Not offhand but it's basically the Unity Particle Pack asset with the Ellen dissolve effect duplicated 100 times. A dev emailed me and confirmed the "buffer == NULL" messages (he's looking into it) but not the crash. I disabled the particle effect while still using the dissolve material and haven't had the message ever since.

 

Same with 2019.3.3f1, using URP.

 

This is also happening to me in a project I just upgraded. I make heavy use of particle systems, and it happens for the particle system I have a sub-emitter on (the parent system uses trails and the child emits following that trail). The issue for me is it seems like I get some spikes/slowdown associated with the errors. (If I turn off the child in the particle system the errors go away)

I'm using the built in render pipeline.

 

I will note for others, I found a way to stop the errors (and the hitches with some flahses)-- by switching out the sub-particle effects to be billboards instead of meshes. This is obviously not an option for everyone who might need the particles to use meshes, but hopefully it helps some for whom that's an acceptable way to get around these errors for now.

 

I have the same error and I see frequent flickering in the Line Renderer.

 

same error with random editor and ingame crashes. I use HDRP

 

Same here.

 

Will this EVER be fixed?

 

Again in new project

 

@mat108 , @Foulcloud ,
Please post which version are you using.

For me, since upgrading to 2019.3.5f1 I don't see the error anymore.

 

In my case, I have this problem with the trail rendered.
I tried the following unity versions ( 2019.3.1f1, 2019.3.5f1, 2020.1.0b1 (beta) ), but the problem persists.

 

Same error, not sure why! I hope it doesn't cause any issues in the playability of our builds!

 

Getting same error here as well. Unity 2019.3.4f1.

 

I had this issue with 2019.3.6f1, but switching Graphics APIs for Windows from "Direct3D11" to "Direct3D12 (Experimental)" solved the issue for me.

Project Settings => Other Settings => AutoGraphics API for Windows (Toggle Off) => + "Direct3D12 (Experimental)" and restart the editor.

 

Same problem here, assert + flickering of the line renderer (seem to become larger = more width, randomly) Does someone have a workaround or a link to a bug entry, or someone from Unity confirms that it is being fixed?

 

Getting this error as well, 2019.3.6f1

 

Looking for the answer on this. Getting it in 2019.3.0f6. Unity, hook it up!

 

Got en email from support: here is the Issue Tracker link (please vote for it, it should help bring it on the top of the pile) issue 1226357: https://issuetracker.unity3d.com/is...uals-null-errors-when-using-a-particle-system

 

Using 2019.3 with built-in render pipeline, everything was fine with my ball and its trail renderer, then I added a particle effect and this error started showing up.

 

I also have a ball with a trail and a particle field that spowns random dots all over the map. Maybe it has something to do with the trail renderer hitting a particle at a bad angle

 

Same here with 2019.3.5f1

Assertion failed on expression: 'task.rasterData.vertexBuffer == NULL'
UnityEngine.GUIUtility: ProcessEvent(Int32, IntPtr)

 

2019.3.6 Happens to me, no trail renderers in the scene, a few particle systems, DX12 selected so that didn't fix it for me. Amazed that no one from Unity has bothered to respond to this.

 

Have the same issue in 2019.3.7f1
It persists since some of 2019.3..
I have Line Renderers in project.

 

same 2019.3.7