Skip to content

Fix for #2769 portal memory leak#2770

Merged
tastybento merged 2 commits intodevelopfrom
2769_portal_memory_leak
Nov 13, 2025
Merged

Fix for #2769 portal memory leak#2770
tastybento merged 2 commits intodevelopfrom
2769_portal_memory_leak

Conversation

@tastybento
Copy link
Member

No description provided.

This uses the portal cooldown function to debounce the events. The
entities immediately enter the portal after they exit because they tend
not to move if there is no player on the other side, however they do not
teleport, so they don't exit.

In addition, the inPortal and inTeleport sets now use ExpiringSet
defensively to remove any values after 10 seconds, which should be more
than enough of time to complete any teleporting. This is defensive code
but will prevent memory leak build up.
@tastybento tastybento changed the title 2769 portal memory leak Fix for #2769 portal memory leak Nov 13, 2025
@tastybento tastybento linked an issue Nov 13, 2025 that may be closed by this pull request
@sonarqubecloud
Copy link

@tastybento tastybento merged commit ac65c5d into develop Nov 13, 2025
3 checks passed
@tastybento tastybento deleted the 2769_portal_memory_leak branch November 13, 2025 06:34
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

Successfully merging this pull request may close these issues.

Portal Memory Leaks

1 participant