Skip to content

Memory management in JVM <-> CLR interop #1

@CoFlows

Description

@CoFlows

CLR <-> JVM acts as an object broker where each side keeps a dictionary reference of the brokered objects references by their native hashcodes. I believe that storing the objects in the Dictionaries doesn't make the eligible for garbage collection.

A proposed solution is to find a points to object function similar to what I believe is being used in PythonNet. I am not sure how it works but just a possible scenario that needs to be understood.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions