Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
112
Found in
2018.4.18f1
2019.3.0b12
2019.3.0f6
2020.1
2020.2
Issue ID
1226357
Regression
Yes
'task.rasterData.vertexBuffer == NULL' errors when using a Particle System
Steps to reproduce:
1. Open User-attached project
2. Run the Sample scene
3. Tab out and wait for at least 3 minutes
Expected: nothing appears in the console
Actual: errors appear in the console
Reproduced in: 2018.4.18f1, 2019.3.0b12, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Not reproduced in: 2019.2.21f1, 2019.3.0b11
Notes: Inconsistent reproduction, versions may not be entirely accurate, the bug may appear sooner than 2019.3.0f5, but I have not been able to reproduce it there
RichardK updated notes: Improved first affected versions based on additional information from QA/community
-
Resolution Note (fix version 2020.2):
Fixed versions:
2020.2.0a8
2020.1.0b8
2019.3.14f1
2018.4.23f1
-
fhsy139291
Nov 07, 2023 15:09
Still happening on version 2019.4.39f1c1
-
Zimorgh
Nov 11, 2020 02:34
Still happening on version 2019.3.6f1
-
aradino
May 22, 2020 02:14
Bug still present in 2019.3.7f1
-
uchimatausa
May 20, 2020 20:10
Contradictory information! Up above this ticket states:
"Fixed versions:
2020.2.0a8
2020.1.0b8
2019.3.14f1
*2018.4.23f1*"While here - https://unity3d.com/unity/qa/lts-releases?version=2018.4
"Known Issues in 2018.4.23f1
* Graphics - General: 'task.rasterData.vertexBuffer == NULL' errors when using a Particle System (1226357)"So what?
-
KospY
May 20, 2020 09:24
It's considered as fixed in Unity 2019.3.14, but in fact it's still happening, please re-open this issue!
-
XochiInteractive
May 09, 2020 07:43
I'm using Unity 2019.3.12 and I receive this error on my Particle System. It will randomly appear between 1 to 5 minutes after run time. If I deactivate the gameobject it never appears, is there a way to resolve this error?
-
ReadyNine
May 07, 2020 08:19
In my case I am having the same problem with the line renderer.
If you disable the Gameobject that contains the line renderer, no symptoms appear.
Unity 2019.3.12f1
-
Laious
May 07, 2020 00:05
EDDYSPAGHETTI, it does. I have players reporting crashes because of this issue. It's only on some machines, but it happens.
-
eddyspaghetti
May 04, 2020 23:36
Having the same issue in 2019.3.11f1, pretty infrequently. I'd love to know the answer to whether or not this has an impact on built games. It LOOKS like it might be an editorGUI only issue, which means we can at least proceed with working in this version while we wait for a fix to land for 2019.3
-
projectawl
May 03, 2020 06:03
Does this impact the final build in any way? Or is it just outputting the error message as an error in itself? Should I worry about publishing with these error messages?
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Debugger stops at commented lines of code when using ECS
- Asset preview doesn't update on changing shader's _GlobalColor property when the shader uses global uniforms
- Crash on GetSpriteAtlasDependenciesFromBinary when opening specific project
- Animation Clip with Legacy enabled does not play when Time.timeScale is set to 0 despite Update mode set to "Unscaled time"
- Rename is enabled on subfolder empty space - "Can't rename to empty name" warning
richardkettlewell
May 07, 2020
Fixed versions:
2020.2.0a8
2020.1.0b8
2019.3.14f1
2018.4.23f1