-
-
Notifications
You must be signed in to change notification settings - Fork 374
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
Potential Memory Leak w/ function local variables #2877
Comments
Can you reproduce this in 2.5-alpha2? |
I'll give it a shot - as stated it takes up to two hours to reproduce as it accumulates and only seems to start after a certain amount of time, but will try. |
Server isn't even booting; has this error about 50 times on 2.5-alpha2 |
Please try without addons, this should have been fixed before 2.4 was released. |
Hard to tell if it's directly continuing without addons but appears to be. |
From digging into a heapdump in a bit more detail, it seems to be setting a variable to something split, for instance:
|
I'm mistaken. The {_lore::*} variable from above was set 16 million times after 4 hours of uptime. I'd presume the local variable isn't being deleted when in list form. |
after doing testing with @Govindass quick solution is to delete local variable at the end of a code
|
Closing in favor of #2337, to consolidate this issue. |
Description
When writing functions (not procedures), storing local variables are potentially causing a memory leak as they do not appear to be deleted once the function returns a value.
Steps to Reproduce
Expected Behavior
Local variables should be fully deleted from the RAM and the server should not keep tracking them.
Errors / Screenshots
Here is a screenshot of the Eclipse Memory Analyser taken during a lagspike.
Server Information
Additional Context
Potentially similar to #2337, though it is marked as closed before 2.4 was released.
The text was updated successfully, but these errors were encountered: