Search Issue Tracker
Fixed in 5.5.0f3
Votes
0
Found in
5.4.0f3
Issue ID
830217
Regression
Yes
[Compute] ComputeBuffers have to be manually Released/Disposed, otherwise crash or errors
Current ComputeBuffer API requires user to manually Release or Dispose the buffer once done, otherwise depending on situation they get either error messages, or crashes once the garbage collector reclaims them.
Reproduction steps:
1. Open the attached project
2. Build the project with the exit scene
3. Observe the application crash as you click the 'exit' button
Instead of quitting the application, it just crashes.
Also added an output_log.txt file with the stack trace.
Everything works with 5.2.4f1, 5.3.6p5 versions of Unity
Crashes in: 5.4.1p1, 5.4.0p4 versions and 5.5.0b4
Comments (4)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
requintueur55
Dec 20, 2018 01:24
I got this issus on unity 2018.3[...] how do I solve it. My project is unworkable now because it's laggy
requintueur55
Dec 20, 2018 01:23
I got this issus on unity 2018.3[...] how do I solve it. My project is unworkable now because it's laggy
requintueur55
Dec 20, 2018 01:23
I got this issus on unity 2018.3[...] how do I solve it. My project is unworkable now because it's laggy
requintueur55
Dec 20, 2018 01:23
I got this issus on unity 2018.3[...] how do I solve it. My project is unworkable now because it's laggy