2018.3.0f2 - Assertion failed on expression and computer crash

Unity Engine
1

I recently updated my project to 2018.3.0f2 and the console in now throwing a lot of errors randomly:

  • Assertion failed on expression: ‘task.rasterData.vertexBuffer == NULL’
    and
  • Assertion failed on expression: ‘task.rasterData.indexBuffer == NULL’

I don’t have any clue of what is happening here. I randomly disabled some gameobjects on my scenes and it “seem” to be related to mesh renderers, but nothing sure.

Does anyone know what I can do to fix this?

Edit: I can confirm that this issue happen when a particle system is in the scene and VR is enabled.

Edit 2: I also suspect that this issue cause the computer to crash when the application quit!

2

Have you filled a bug report?

3

Unfortunately I can’t reproduce it on a new project (I assume I should not send a 50gb project to your support team).
I was mainly looking about some clues about where to look (the error don’t give any indication, it also don’t focus on any object).
Anyway I will try to send a bug report without a repro project. Hope I will get some help about this.

4

I am getting this problem also upon updating to 2018.3.0f2… Our project uses the Mirza Beig particle fx package. Here:

This error occurs when a disabled pfx gameobject is enabled at runtime.

1 Like
5

Could you please submit a bug-report and include a project to reproduce the issue, as described in this document:

Submitting a bug-report allows Unity Technologies to take a look at this issue.

After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. You can post this Case number here (in this forum thread) for Unity staff to pick up, in case they see this post.

1 Like
6

I get this problem in Unity 2018.3.0f2 as well as long as both of these conditions are met:

  1. Add any particle system to the scene (I tried particles from a couple different packs).

  2. Run it in VR mode (I tried with the Rift).

2 Likes
7

And memory usage increases about 10MB per second if you hit stop and play again after the error shows. This causes both the Editor or game crashes. And in our situation, we cannot just downgrade our project to a lower version for the new prefab system. Please fix it.

Here is my Case number 1112834.

8

Interesting, my game crash randomly when the player quit since 2018.3.
It cause the graphic driver to crash and the computer to froze (only way to fix is rebooting).
It could be related to this issue.
When the game crash, the log file is full of this line: “d3d11: attempt to lock null buffer”

This issue is pretty serious and need to be fixed ASAP. Thanks!

9

Same issue here for Tales Of Glory (VR game).

Game crashes on exit when calling Application.quit(). Reproduced by every ppl playing on beta.

Editor crashes too when stopping play mode.

Crashes are pretty hard, need a full reboot.

I can’t downgrade too. i’m stuck waiting for a fix.

If unity team can check it !

Thanks

Jay

10

Please submit bug report as mentioned here:

If they don’t have a bug report with a project to reproduce the problem on, they can’t fix it.

11

@Peter77 RSmart already created a bug report.
Do we need to create another one?
Also I can’t create a repro project for the crash as it’s a random issue for me.
Hope the “Assertion failed” issue is related to the crash.

12

If getting a bug fix is important to me and I have a project to reproduce the issue, I submit a bug-report.

Otherwise, even if another person submitted a report already, it might not get fixed, because it could be a different issue the other person reported.

Thus, if you don’t submit a report with a project to reproduce the issue, do not expect that Unity Technologies is providing a bug-fix. This is just from my past experience.

13

Don’t worry guys. My report is subbmit with a very simple project and a instruction to reproduce it in a empty project. And also you can try it here.

1.Create a empty project with Unity2018.3.0f2. And add a ParticleSystem to the scene.
2.Make sure VR HMD is tracked.(VR supported in PlayerSettings)
3.Run SampleScene
4.Stop SampleScene.
5.Run again and click console tab, game tab or scene tab.
6.Assertion failed on expression: ‘task.rasterData.vertexBuffer == NULL’ shows
7.Stop and Run again.
8.Checking the memory usage by UnityEditor.

4 Likes
14

I’m also having this problem. @RSmart , can you post a link to the issue tracker so the rest of us can vote on it?

1 Like
15

It’s not the RSmart one, but here is a link to this case:

2 Likes
16

Unity QA team says my report is the same as this one by email. Let’s just vote this.

17

As of jan 25, this bug is still there!.. How absurd of a situation where you can’t use ANY PARTICLE system in Unity 2018.3 without getting this error. I know they are working on a fix but is there a work around in the mean time?

18

What is the status???

19

your project in check Light Shadows On/OFF
if On then turn Off the shadow after again play problem solve…

2 Likes
20

I was having the same issue, but appears to be fixed after upgrading to 2018.3.4f1