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.

Sign up for GitHub

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

Jump to bottom

Figure out why the RIO memory leaks after a couple deploys #9

Closed
TheComputer314 opened this issue Nov 12, 2023 · 13 comments
Closed

Figure out why the RIO memory leaks after a couple deploys #9

TheComputer314 opened this issue Nov 12, 2023 · 13 comments
Assignees
@TheComputer314
Labels
Bug An issue with the robot code that prevents something from working properly. CRITICAL Absolute top priority, robot WILL NOT work until this is fixed.

Comments

@TheComputer314
Copy link
Contributor

No description provided.

@TheComputer314
Copy link
Contributor Author

#4 (comment)

First mentioned here

@TheComputer314 TheComputer314 self-assigned this Nov 12, 2023
@TheComputer314 TheComputer314 added Bug An issue with the robot code that prevents something from working properly. CRITICAL Absolute top priority, robot WILL NOT work until this is fixed. labels Nov 12, 2023
@TheComputer314 TheComputer314 added this to the Central Missouri Regional milestone Nov 12, 2023
@TheComputer314
Copy link
Contributor Author

  • Tried memory profiling... gave up
  • Straight up deleted Phoenix 6
  • For some reason that fixed the issue
  • New issue: We don't have a Pigeon lmao

@TheComputer314
Copy link
Contributor Author

My laptop might be the cause... It's not happening with the old driver station laptop

If we get the issue again with other laptops we should reopen this issue, but for now, problem solved.

@TheComputer314
Copy link
Contributor Author

It's happening again and it's not just a my laptop issue this time

@TheComputer314
Copy link
Contributor Author

So we thought it was an issue with the robot code from a previous deploy not getting its process killed cleanly, but that appears to not be the case since it did happen with a clean kill. Also sometimes the RIO just completely freezes up and requires a reboot.

@TheComputer314
Copy link
Contributor Author

https://www.chiefdelphi.com/t/openjdk-not-enough-space-java-error/446222/10

wpilibsuite/2024Beta#39

We found the issue on chiefdelphi

@TheComputer314
Copy link
Contributor Author

New beta release, hopefully should be fixed but we don't have the robot rn

@TheComputer314
Copy link
Contributor Author

It appears to be fixed with the new beta firmware.

@TheComputer314
Copy link
Contributor Author

IT WASN'T FIXED

@TheComputer314 TheComputer314 reopened this Jan 5, 2024
@TheComputer314
Copy link
Contributor Author

NOW ITS MAKING SEGMENTATION FAULTS

@TheComputer314
Copy link
Contributor Author

Nvm the segfault was because PathPlanner didn't properly make path files

@TheComputer314
Copy link
Contributor Author

The RAM usage was still worrying though, it might still be not completely fixed

@TheComputer314
Copy link
Contributor Author

It probably is fixed.

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

@TheComputer314 TheComputer314

Labels
Bug An issue with the robot code that prevents something from working properly. CRITICAL Absolute top priority, robot WILL NOT work until this is fixed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TheComputer314