-
Notifications
You must be signed in to change notification settings - Fork 931
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Particle emitter has a huge memory issue #6125
Comments
Could this be a related issue that was reported in here? |
Maybe? but really high ram usage was never mentioned or talked about in it. though a memory leak is indeed mentioned. I opened the project of that issue and the ram usage does indeed increase about as much as this one if maybe a little slower so it is related. It would also appear this memory issue also leaks into the editor as I left it running until it consumed 5GB of ram, closed the preview and now it's staying at 1.2GB of ram usage versus before where it was around 80mb for that process. |
could also be related to your issue #6003 (even if not 3d) |
Was the issue with the 3D particle emitter or the 2D one? |
This specific issue is for the 2D particle emitter. Refer to the test project included in this post alongside the screenshot |
After leaving the bug report test project running on background for half an hour, I can confirm that this bug has indeed been fixed |
Thank you for testing it |
Is there an existing issue for this?
Describe the bug
As the title suggests, there is a huge memory issue regarding the particle emitter where it acts as it doesn't get deleted, even though it should resulting in huge amount of ram usage. This doesn't also go away if you reload the scene or go to another, the ram usage stays the same.
MemoryLeakFoundPartThree.zip
Steps to reproduce
Instructions also included in test project
GDevelop platform
Desktop, Web, Mobile
GDevelop version
5.3.186
Platform info
Windows 10 LTSC 21H2 (OS Build 19044. 1288)
Additional context
No response
The text was updated successfully, but these errors were encountered: