Skip to content
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

Poor memory management when changing scenes causing permanent memory increase #5921

Open
1 task done
ZachjuKamashi opened this issue Nov 17, 2023 · 2 comments
Open
1 task done

Comments

@ZachjuKamashi
Copy link

ZachjuKamashi commented Nov 17, 2023

Is there an existing issue for this?

Describe the bug

There is a permanent memory increase after changing scenes with regarding events which can result in very high RAM usage in certain cases, enough for the project to run out of memory and even crash devices.

Here is a video showcasing how the memory usage performs with this test project.

vokoscreenNG-2023-11-17_22-37-40.mp4

And here is the project file

Memory_leak-iter3.zip

Steps to reproduce

Instructions are within the Project

GDevelop platform

Desktop, Web, Mobile

GDevelop version

5.3.185

Platform info

Windows 10 Enterprise LTSC 21H2 OS Build 19044.1288

Additional context

No response

@D8H
Copy link
Collaborator

D8H commented Dec 6, 2023

This is probably because the generated code is clearing object lists before the events instead of after them so some instances stays in memory until the scene is run again.

@ZachjuKamashi
Copy link
Author

@D8H It's been half a year, are there any updates on solving this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants