Skip to content
This repository was archived by the owner on Nov 9, 2022. It is now read-only.
This repository was archived by the owner on Nov 9, 2022. It is now read-only.

NodeMainExecutorService leaks RosActivity through NodeMainExecutorServiceListener #254

Closed

Description

@stratomda

When a RosActivity is destroyed, and the main application is still running, the NodeMainExecutorService contains a reference to the RosActivity preventing it from gc. The fix is to add the ability to remove the NodeMainExecutorServiceListener created in the RosActivity from the NodeMainExecutorService ListenerGroup. This requires ListenerGroup to contain a method for removing a listener (bug filed in rosjava/rosjava_core rosjava/rosjava_core#233).

Activity

  1. added a commit that references this issue on Mar 3, 2017
    779bc8b
  2. jubeira commented on Mar 14, 2017

    @jubeira

    This was fixed for Indigo but not for Kinetic yet, am I right?

  3. stratomda commented on Mar 14, 2017

    @stratomda
    ContributorAuthor

    That seems to be correct.

  4. adamantivm commented on Mar 14, 2017

    @adamantivm
    Contributor

    That was my fault, I screwed something up when I tried to do the update - I got the 0.3.2 to release but failed to push upstream from my local copy. It should be fixed now, but I'd appreciate a second pair of eyes.

  5. jubeira commented on Mar 14, 2017

    @jubeira

    LGTM; I think this issue can be closed now.

  6. stratomda commented on Apr 17, 2017

    @stratomda
    ContributorAuthor

    @adamantivm is this issue still open or was it merged into 0.3.3?

  7. adamantivm commented on Apr 18, 2017

    @adamantivm
    Contributor

    It's merged and published!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions