-
Notifications
You must be signed in to change notification settings - Fork 771
Free monitorEnterRecordPool in freecontinuation #22792
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
Conversation
4e8b114
to
be20f4a
Compare
jenkins test sanity xlinux64 jdk25 |
jenkins test sanity alinux64 jdk25 |
machine issues, Ill try the test again |
jenkins test sanity alinux64 jdk25 |
jenkins compile xlinux jdk25 |
Lots of |
Currently, the monitor enter record pool is only free'd when the continuation is removed from the continuation cache. This behaviour causes memory leaks as a continuation may never be removed from the cache. Additionally, when allocate a new continuation each time enterContinuation is called. This PR takes the conservative approach of free the monitor records as soon as the continuation is free'd. In future we should consider if the monitor records can be persisted run to run. Currently, this has not been tested yet. Fixes: eclipse-openj9#22776 Signed-off-by: tajila <[email protected]>
jenkins test sanity alinux64 jdk25 |
jenkins test sanity.openjdk amac jdk25 |
timeout in java/lang/Thread/virtual/Collectable.java which is #18463 |
Currently, the monitor enter record pool is only free'd when the
continuation is removed from the continuation cache. This behaviour
causes memory leaks as a continuation may never be removed from the
cache.
Additionally, when allocate a new continuation each time
enterContinuation is called.
This PR takes the conservative approach of free the monitor records as
soon as the continuation is free'd. In future we should consider if the
monitor records can be persisted run to run. Currently, this has not
been tested yet.
Fixes: #22776