Make sure objects are created and destroyed at the right times #44
Labels
No labels
board:etc.eos
bug
duplicate
enhancement
help wanted
invalid
licensing
needs triage
new board
platform:android
question
regression
ui
wontfix
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
UniversalFocusRemote/tasks#44
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Now that pretty much the whole app has been rewritten, I need to go through again and make sure all of the garbage collection works as intended. All the objects are so small that tbh a memory leak wouldn't be that bad lol but I wanna do things the right way. Also having a board object stick around after "disconnecting" from the board has potential to cause Issues.
I did check the board object itself and it seems like it gets destroyed properly, need to check all of the children though. Might be worth seeing if there's some sort of profiler I can use so I don't just have to manually add debug statements to all of the destructors to check for this.