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

Happens in 2018.4.19f1 with ParticleSystems using procedural mesh as emitter shape.

 

Try resetting the line rendered to its default material, the line rendered requires a specific material which I forgot what it was.

 

Here it is : https://docs.unity3d.com/Manual/shader-StandardParticleShaders.html

 

it happens to me as well when I use Lines. dunno what causes it and after repeatedly starting the game for a few times it just doesn't show up any more

 

2019.3.6-7-8 here.
Error appeared after starting to use particle system. Nothing special on particleSystem, Material is URP/Particles/Unlit and a texture on it.

 

same 2019.3.8 with my trail renderer.

 

Seems to be ParticleSystem with Shadows and LineRenderer/TrailRenderer in the same scene
I can reproduce this bug in all the 2019.3.x versions that I have:
Create New Project
- Add a ParticleSystem, goto Renderer-Tab and turn on "Cast Shadows"
- Add a LineRenderer to the scene
- Both Particle System and LineRenderer must be visible in either Game or Scene window!
- Press Play, wait a few seconds...

 

I just updated from 2018.4.10f1 to 2018.4.20f1 and started getting these errors.

I have Mesh particle emitters and Line Renderers, but nothing is receiving or casting shadows.

 

Yep started getting this today on 2019.3.7.f1

 

Assert is still present in 2019.3.9f1

 

2019.3.3 having this problem when particle system is activated during gameplay. And trail renderer is active when this error is thrown.

 

Unity 2018.4.20 and the same thing. Could be line renderers, could be some particle systems.

 

Ah, yes, this seems to be happening with Particle Systems on my Prefab GameObjects that I instantiate at runtime. I have a main menu scene that has the same particle emitters already instantiated and it doesn't error.

 

This is a bug and someone already reported it.
The best we can do now is vote on the issue to get Unity's attention and wait for a fix.

Vote here (issue 1226357): https://issuetracker.unity3d.com/is...uals-null-errors-when-using-a-particle-system

 

I upvoted that, I also mentioned the issue in a Crash report I sent to Unity...

 

Same probrem 2018.4.21f1

 

Updated from 2018.4.16 to 2018.4.21, now this spams repeatedly. Runtime instantiated torches using particle systems with billboard renderers are causing it. Turning them on/off starts/stops the errors.

 

Still happening in 2019.3.10f1. I think it's crashing my graphics driver occasionally too.

 

For me, seems like it happens especially if I pause the game.

 

Hate to add to the mix, I am also getting this 2019.3.1f1

 

Hey, can you verify that this is fixed in my repro scene as well? I think the difference is I'm using a custom mesh in the particle, so the stack trace ends up slightly different than what is supposedly about to be fixed. Case #1240718 - need to add a trail or line as well, added while in play mode and forgot to re-add outside of play mode before submitting bug. The stack trace here is the same as the one that crashes our game (releasing very soon!) but I couldn't manage to get the repro to crash as reliably.

edit: also! It seems that in our game, this error does not crash our game when Dynamic Batching is disabled! This is unacceptable to disable in our game for performance reasons, of course, but worth noting to help you guys track it down.

 

Hi, where can I get 2020.1.0b8? Unity Hub shows latest 2020.1.x version as 2020.1.0b6 and I'm using it already and still getting the errors with line renderer. I didn't want to use alpha but I will try it to see if it fixes this issue.

 

b8 has not been released yet, they're at b6 at the moment. It seems they release a new beta every week (link).

Assuming they continue the weekly release, knowing b6 was released April 24th (Friday) and considering their announcement to release on Wednesday rather than Friday (link), we should expect to see b8 either on May 6th or May 13th.

 

The problem seems to have been solved in Unity 2020.2.0a8.

 

Still on 2019.3.11f1

 

Unity staff wrote it's going to be fixed in 2019.3.13f1:
https://forum.unity.com/threads/201...-vertexbuffer-null.818181/page-2#post-5757937

 

2019.3.11f1 happening when Particle System and Line Renderer are in the same scene.

 

same issue in 2019.3.11f1.
Added a particle system that activates on my shots and now my console is spammed with this notification when I shoot enemies.
Does this effect my final build? Does the error actually mean anything or is it just a weird error that shows an error message?

 

I tried to build my small game that also shows this error.. builds did succeed and I didnt find any bugs on it.. maybe there are for other people but mine didnt have any

 

Can I ask the unkind question as to why things this debilitating make it into 2018.4 LTS versions?
I had recently gotten over my extreme fear of upgrading Unity, and now it is back in full force.

 

Worked for me too.

 

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

 

I don't know if it's "valuable" or not, but If this error is the reason why unity randomly crashes when i try to render particles via commandBuffer, this error cost me and 3 other people with families their jobs.

 

Hoping for 2019.3.14 soon!
We are getting this error with the editor and game crashes some what frequently over the last 3~4 weeks.
We have a bug submitted (Case:1247954)

Is the crash part and flickering line renders of this issue going to be resolved in 3.14 or are these separate issues?

We get these errors but not 100% sure they are linked to the crashes. For any one else experiencing crashes do you see these in your crashes?

[Editor]
CreateDirect3D11SurfaceFromDXGISurface
ERROR: SymGetSymFromAddr64, GetLastError: 'Attempt to access invalid address.' (Address: 00007FF62620A8EE)
0x00007FF62620A8EE (Unity) (function-name not available)

[Standalone Windows]

Stack Trace of Crashed Thread 12484:
0x00007FFDBD60A924 (d3d11) D3D11CoreCreateDevice
0x00007FFDBD6093D2 (d3d11) D3D11CoreCreateDevice
0x00007FFDBD60C1F3 (d3d11) D3D11CoreCreateDevice
0x00007FFDBD60CBCF (d3d11) D3D11CoreCreateDevice
0x00007FFDBD60D3C0 (d3d11) D3D11CoreCreateDevice
0x00007FFDBD6026AA (d3d11) D3D11CoreCreateDevice
0x00007FFDBD625FD2 (d3d11) D3D11CoreGetLayeredDeviceSize
0x00007FFDBD625F92 (d3d11) D3D11CoreGetLayeredDeviceSize
0x00007FFD5CED5B09 (UnityPlayer) CreateDefaultSRV
0x00007FFD5CED8D77 (UnityPlayer) TexturesD3D11Base::RegisterNativeTexture
0x00007FFD5CECF753 (UnityPlayer) GfxDeviceD3D11Base::RegisterNativeTexture
0x00007FFD5CF94BD3 (UnityPlayer) GfxDeviceWorker::RunCommand
0x00007FFD5CF9C6AD (UnityPlayer) GfxDeviceWorker::RunExt
0x00007FFD5CF9C7A5 (UnityPlayer) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FFD5D932C5D (UnityPlayer) Thread::RunThreadWrapper
0x00007FFDC41F7974 (KERNEL32) BaseThreadInitThunk
0x00007FFDC433A271 (ntdll) RtlUserThreadStart

 

Can you please make a new thread in the relevant forum? This doesn't seem to be related to the thread in any way.

 

Yeah I can make a new thread with my specific details.

Quite a few people, in this thread have mentioned related crashes with this issue. We see this error in the logs before a majority of our recent crashes.

I am just trying to clarify what is "fixed" ?

From an end user perspective, does that just mean the error won't appear in the console or are there other known issues caused by this?

For future readers it's worth to clarify what should be expected from this fix and what issues are not related.

 

Just for closure, I encountered a similar crash w/ particles using 2019.3.9f1. This is what customer QA said:
"Thank you for reporting this issue. After a further search, I found this issue internally fixed for Legacy XR in 2019.3.15f1 which should be released sometime in the future (current version is 2019.3.14f1). Also, this issue is fixed in XR SDK which you can enable in Project Settings."

 

We downloaded Unity 2019.3.14f1 and are still getting our crash and the same assertion error. Sent the updated logs and dmp to case 1247954.

Is anyone seeing the issue resolved on 14?

Assertion failed on expression: 'task.rasterData.indexBuffer == NULL'
(Filename: C:\buildslave\unity\build\Runtime/GfxDevice/GeometryJob.cpp Line: 199)

Crash!!!
SymInit: Symbol-SearchPath: 'C:/Program Files/Unity/Hub/Editor/2019.3.14f1/Editor/Data/Mono;.;C:\Users\rich\Documents\GitBoxVR;C:\Program Files\Unity\Hub\Editor\2019.3.14f1\Editor;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 534, UserName: 'rich'
OS-Version: 10.0.0
C:\Program Files\Unity\Hub\Editor\2019.3.14f1\Editor\Unity.exe:Unity.exe (00007FF61FA80000), size: 136282112 (result: 0), SymType: '-deferred-', PDB: '', fileVersion: 2019.3.14.13067
Assertion failed on expression: 'task.rasterData.vertexBuffer == NULL'
UnityEditor.EditorGUIUtility:RenderPlayModeViewCamerasInternal_Injected(RenderTexture, Int32, Vector2&, Boolean, Boolean)
UnityEditor.EditorGUIUtility:RenderPlayModeViewCamerasInternal(RenderTexture, Int32, Vector2, Boolean, Boolean)
UnityEditor.PlayModeView:RenderView(Vector2, Boolean)
UnityEditor.GameView:OnGUI()
System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception&)
System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)
System.Reflection.MethodBase:Invoke(Object, Object[])
UnityEditor.HostView:Invoke(String, Object)
UnityEditor.HostView:Invoke(String)
UnityEditor.HostView:InvokeOnGUI(Rect, Rect)
UnityEditor.DockArearawView(Rect, Rect)
UnityEditor.DockArea:OldOnGUI()
UnityEngine.UIElements.IMGUIContaineroOnGUI(Event, Matrix4x4, Rect, Boolean, Rect, Action, Boolean)
UnityEngine.UIElements.IMGUIContainer:HandleIMGUIEvent(Event, Matrix4x4, Rect, Action, Boolean)
UnityEngine.UIElements.IMGUIContaineroIMGUIRepaint()
UnityEngine.UIElements.UIR.RenderChainCommand:ExecuteNonDrawMesh(DrawParams, Boolean, Single, Exception&)
UnityEngine.UIElements.UIR.UIRenderDevice:EvaluateChain(RenderChainCommand, Rect, Matrix4x4, PanelClearFlags, Texture, Texture, Texture, Single, NativeArray`1, NativeArray`1, Exception&)
UnityEngine.UIElements.UIR.UIRenderDevicerawChain(RenderChainCommand, Rect, Matrix4x4, PanelClearFlags, Texture, Texture, Texture, Single, NativeArray`1, NativeArray`1, Exception&)
UnityEngine.UIElements.UIR.RenderChain:Render(Rect, Matrix4x4, PanelClearFlags)
UnityEngine.UIElements.UIRRepaintUpdaterrawChain(Rect, Matrix4x4)
UnityEngine.UIElements.UIRRepaintUpdater:Update()
UnityEngine.UIElements.VisualTreeUpdater:UpdateVisualTreePhase(VisualTreeUpdatePhase)
UnityEngine.UIElements.Panel:UpdateForRepaint()
UnityEngine.UIElements.Panel:Repaint(Event)
UnityEngine.UIElements.UIElementsUtilityoDispatch(BaseVisualElementPanel)
UnityEngine.UIElements.UIElementsUtilityrocessEvent(Int32, IntPtr)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

Hello,

Maybe the reason it was listed as Known Issue because it's not corrected. we are still having the same issue on 2019.3.14...
This is a real handicap for indep VR dev, causing games to crash randomly.

Is it possible to reopen the issue: https://issuetracker.unity3d.com/is...23.1884356547.1589916837-307983131.1586452505

 

For sure it's frustrating because we (VR devs) already had the same error you followed 1 year ago. It's back and blocking releases.
https://issuetracker.unity3d.com/issues/vr-particle-systems-cause-task-dot-rasterdata-dot-indexbuffer-equals-equals-null-error-and-lead-to-graphical-glitches?_ga=2.210732053.1884356547.1589916837-307983131.1586452505

 

I've submitted a new case, Case 1249092 - which links to case 1248799 - which has my project on Google Drive for you guys to access. I cannot make a small repro project, but this issue could be blocking our very fast approaching Stadia release.