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

[Bug] Memory Leak when Saving and Quitting #5029

Open
Snailman11 opened this issue Dec 21, 2024 · 1 comment
Open

[Bug] Memory Leak when Saving and Quitting #5029

Snailman11 opened this issue Dec 21, 2024 · 1 comment
Labels
P0 Bug Completely gamebreaking or catastrophic bugs

Comments

@Snailman11
Copy link
Collaborator

Snailman11 commented Dec 21, 2024

Describe the bug

When Saving and Quitting Pokerogue, a memory leak occurs.
-Memory used is increased by 0.2 to 0.3 GB at a consistent rate.
-Occurs independently of how the run was loaded. (Continue/Load Game)
-Occurs with any Run
-Occurs with any Browser or Device
-Occurs both Online and with Localhost.

When the Browser is refreshed, memory used decreases drastically.

Link to Discord's Bug Report (memory leak)
https://discord.com/channels/1125469663833370665/1320050193567186984

Reproduction

Load a run, then Save and Quit. Keep doing this until your RAM usage is extremely high.

Expected behavior

There should not be a memory leak.

Screenshots / Videos

Memory Leak Save and Quitting1

Memory Leak Save and Quitting2

Session export file

No response

User data export file

No response

Additional context

No response

@Snailman11 Snailman11 added the P0 Bug Completely gamebreaking or catastrophic bugs label Dec 21, 2024
@Snailman11 Snailman11 moved this from To triage to Ready in PokéRogue Bug Management Dec 21, 2024
@Wlowscha
Copy link

Probably related: every time I attempt to run the full test suite on the beta branch, after some time (fifteen minutes or so) the test crashes citing memory leaks issues. I have not been able to replicate this for individual folders in test, although I probably missed some. I attach a screenshot for reference.
some_error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 Bug Completely gamebreaking or catastrophic bugs
Projects
Status: Ready
Development

No branches or pull requests

2 participants