Skip to content

Actor handles may cause memory leak in core worker #6370

@raulchen

Description

@raulchen

Describe the problem

Currently, CoreWorker keeps a map of all known actor handles, this map is only cleaned up when a non-actor task finishes, see here.

This could cause memory leak in some cases, e.g., an actor with a method which takes an actor handle as its parameter.

To fix this, we should remove the actor handle from the map when the corresponding Java/Python object is GC'ed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleThe issue is stale. It will be closed within 7 days unless there are further conversation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions