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

Support allocation into a non-moving space #102

Open
udesou opened this issue Sep 11, 2023 · 0 comments
Open

Support allocation into a non-moving space #102

udesou opened this issue Sep 11, 2023 · 0 comments

Comments

@udesou
Copy link
Contributor

udesou commented Sep 11, 2023

Some objects such as types, and type names, which are used as metadata when scanning objects, should be allocated into a non-moving space. While MMTk already provides an API for doing so, and there's already a PR to add this support to Julia, MMTk currently allocates these objects in the immortal space; For this reason, they never get collected and increase memory consumption leading to OOM errors in the CI (#101). This issue is to keep track of this problem, which should be solved after we are able to allocate such objects in a proper non-moving space, such as marksweep (which has a few issues in mmtk-core at the moment: mmtk/mmtk-core#688).

NB: In the moving immix version (#93) the non-moving characteristic has been achieved by pinning these objects indefinitely.

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

1 participant