Memory Leak on ADStar Planning

[scarmain]

Describe the bug I was looking at memory usage on the Rio 1 for our robot, and it looks like ADStar planning is going crazy allocating objects. I'm writing this down just to document it, not sure how to diagnose further. It seems to be allocating 4x more objects per second from our robot code

To Reproduce Steps to reproduce the behavior:

1. I followed the steps to connect to the robot with VisualVM (https://docs.wpilib.org/en/stable/docs/software/advanced-gradlerio/profiling-with-visualvm.html#analyzing-a-heap-dump) This could connect to simulation too, but my screenshots are from the robot.
2. Code at https://github.com/FRC2832/Robot2832-2025Kitbot, but the snapshots were taken while disabled, no driving started. No team code directly called ADStar to my knowledge (we do have calls to PathPlanner DriveToPose, but not executed yet when this was measured).

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Versions: (please complete the following information):

• Rio 1
• PPLib Version: 2025.2.1
• PPLib Language: Java

Additional context Add any other context about the problem here.

[Baconing]

I also have this, did you ever fix it or are you still waiting for a response?

[owen300]

my team also has this issue