Search Unity

  1. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice
  2. Ever participated in one our Game Jams? Want pointers on your project? Our Evangelists will be available on Friday to give feedback. Come share your games with us!
    Dismiss Notice

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

Discussion in 'Editor & General Support' started by Aksirpg, Jan 29, 2020.

  1. Aksirpg

    Aksirpg

    Joined:
    Nov 20, 2018
    Posts:
    2
    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.
     
  2. silenterus

    silenterus

    Joined:
    Nov 8, 2019
    Posts:
    8
    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.
     
    Skunk-Software likes this.
  3. mustardbucket1234

    mustardbucket1234

    Joined:
    Mar 20, 2015
    Posts:
    4
    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
     
  4. hertz-rat

    hertz-rat

    Joined:
    Nov 3, 2019
    Posts:
    70
    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...
     
    Goty-Metal likes this.
  5. Aksirpg

    Aksirpg

    Joined:
    Nov 20, 2018
    Posts:
    2
    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?
     
    chrisrhodesy and Lance_JZ like this.
  6. hertz-rat

    hertz-rat

    Joined:
    Nov 3, 2019
    Posts:
    70
    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.
     
    Last edited: Feb 1, 2020
  7. glenneroo

    glenneroo

    Joined:
    Oct 27, 2016
    Posts:
    48
    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...
     
  8. TheQuad

    TheQuad

    Joined:
    Dec 28, 2018
    Posts:
    8
    Did someone report it?
     
  9. burn_barrel

    burn_barrel

    Joined:
    May 2, 2018
    Posts:
    2
    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.
     
    DINmatin likes this.
  10. camsha

    camsha

    Joined:
    Nov 18, 2013
    Posts:
    9
    Exactly the same situation here.
     
  11. Biosoftworld

    Biosoftworld

    Joined:
    Jan 24, 2019
    Posts:
    3
    I have upgrade today from 2019.2 to 2019.3 and I have the same problem in every porject.
     
    DINmatin likes this.
  12. ratneshpatel

    ratneshpatel

    Joined:
    Oct 10, 2017
    Posts:
    20
    I tested this. I am getting this error for Smoke particle effects and Line renderer too.
     
  13. glenneroo

    glenneroo

    Joined:
    Oct 27, 2016
    Posts:
    48
    Still happening with 2019.3.1f1.
     
  14. Gloubi88

    Gloubi88

    Joined:
    Mar 30, 2015
    Posts:
    5
    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.
     
    bobchalmers and Dragnipurake97 like this.
  15. perza

    perza

    Joined:
    Jun 30, 2013
    Posts:
    6
    Same here
     
  16. DJ_DiX

    DJ_DiX

    Joined:
    Aug 1, 2017
    Posts:
    4
    Same. Rolling back to 2019.3.0b11
     
  17. SozoDev

    SozoDev

    Joined:
    Nov 15, 2016
    Posts:
    12
    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?
     
  18. TheKiwiCoder58

    TheKiwiCoder58

    Joined:
    May 15, 2013
    Posts:
    38
    Also getting this error. Turning off particles fixes it for me. Running 2019.3.0f6
     
    IlisanVlad and bobchalmers like this.
  19. pbritton

    pbritton

    Joined:
    Nov 14, 2016
    Posts:
    66
    Can anyone at Unity indicate if this is an issue we should be concerned about?
     
  20. Decimalis

    Decimalis

    Joined:
    Dec 1, 2018
    Posts:
    1
    Happening to me as well, it's definitely a line renderer's cause there...
     
  21. glenneroo

    glenneroo

    Joined:
    Oct 27, 2016
    Posts:
    48
    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?
     
    bobchalmers likes this.
  22. glenneroo

    glenneroo

    Joined:
    Oct 27, 2016
    Posts:
    48
    Still happening in 2019.3.2f1.
     
    Jack00X3 and moodonne like this.
  23. rmon222

    rmon222

    Joined:
    Oct 24, 2018
    Posts:
    60
    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.
     
  24. mat108

    mat108

    Joined:
    Aug 24, 2018
    Posts:
    5
    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.
     
  25. dCalle

    dCalle

    Joined:
    Dec 16, 2013
    Posts:
    45
    I found this infobox. but can't hit Apply to Systems
     

    Attached Files:

  26. linojon

    linojon

    Joined:
    Aug 25, 2014
    Posts:
    111
    Got a link to the case?
     
    Dragnipurake97 likes this.
  27. rmon222

    rmon222

    Joined:
    Oct 24, 2018
    Posts:
    60
    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.
     
  28. Storm4_

    Storm4_

    Joined:
    Mar 2, 2016
    Posts:
    12
    Same with 2019.3.3f1, using URP.
     
  29. Keegan_ORourke

    Keegan_ORourke

    Joined:
    Jun 22, 2015
    Posts:
    3
    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.
     
  30. Keegan_ORourke

    Keegan_ORourke

    Joined:
    Jun 22, 2015
    Posts:
    3
    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.
     
    glenneroo likes this.
  31. Tona999

    Tona999

    Joined:
    Nov 18, 2015
    Posts:
    6
    I have the same error and I see frequent flickering in the Line Renderer.
     
    BlueBananaProductions likes this.
  32. MartinWorker

    MartinWorker

    Joined:
    Feb 24, 2015
    Posts:
    11
    same error with random editor and ingame crashes. I use HDRP
     
  33. Foulcloud

    Foulcloud

    Joined:
    Mar 23, 2014
    Posts:
    4
    Same here.
     
  34. pinkmustachecat

    pinkmustachecat

    Joined:
    Nov 9, 2019
    Posts:
    4
    Will this EVER be fixed?
     
  35. mat108

    mat108

    Joined:
    Aug 24, 2018
    Posts:
    5
    Again in new project

     
  36. glenneroo

    glenneroo

    Joined:
    Oct 27, 2016
    Posts:
    48
    @mat108 , @Foulcloud ,
    Please post which version are you using.

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

    fergamboa_

    Joined:
    Feb 25, 2019
    Posts:
    1
    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.
     
  38. DethKwok

    DethKwok

    Joined:
    Mar 13, 2017
    Posts:
    1
    Same error, not sure why! I hope it doesn't cause any issues in the playability of our builds!
     
  39. Ghetaldus

    Ghetaldus

    Joined:
    Jul 15, 2017
    Posts:
    11
    Getting same error here as well. Unity 2019.3.4f1.
     
  40. maormenashe

    maormenashe

    Joined:
    Oct 7, 2018
    Posts:
    20
    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.
     
    Last edited: Mar 22, 2020
  41. _dns_

    _dns_

    Joined:
    Sep 6, 2013
    Posts:
    12
    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?
     
  42. CDF

    CDF

    Joined:
    Sep 14, 2013
    Posts:
    853
    Getting this error as well, 2019.3.6f1
     
  43. sincerelysleepy

    sincerelysleepy

    Joined:
    Jan 15, 2019
    Posts:
    2
    Looking for the answer on this. Getting it in 2019.3.0f6. Unity, hook it up!
     
  44. _dns_

    _dns_

    Joined:
    Sep 6, 2013
    Posts:
    12
  45. bgmulti15a

    bgmulti15a

    Joined:
    Feb 9, 2017
    Posts:
    23
    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.
     
  46. CGPepper

    CGPepper

    Joined:
    Jan 28, 2013
    Posts:
    140
    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
     
  47. Gaspedal

    Gaspedal

    Joined:
    Mar 29, 2009
    Posts:
    369
    Same here with 2019.3.5f1 :(

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

    MikeUpchat

    Joined:
    Sep 24, 2010
    Posts:
    907
    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.
     
  49. Mccbbi

    Mccbbi

    Joined:
    Feb 8, 2015
    Posts:
    9
    Have the same issue in 2019.3.7f1
    It persists since some of 2019.3..
    I have Line Renderers in project.
     
    geraldp48 likes this.
  50. mrCharli3

    mrCharli3

    Joined:
    Mar 22, 2017
    Posts:
    576
    same 2019.3.7
     
    ShadowAngel and geraldp48 like this.
unityunity