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.

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

Ensure that Sidenoder closes adb and rclone #34

Open
MikeRatcliffe opened this issue Sep 14, 2024 · 0 comments · May be fixed by #40
Open

Ensure that Sidenoder closes adb and rclone #34

MikeRatcliffe opened this issue Sep 14, 2024 · 0 comments · May be fixed by #40

Comments

@MikeRatcliffe
Copy link

Sidenoder has a tendency to leave adb and rclone open when it's closed.

We need to close them when Sidenoder is closed.

MikeRatcliffe added a commit to MikeRatcliffe/sidenoder that referenced this issue Sep 14, 2024
Fixes VRPirates#34

Cleanly closes `adb` and `rclone` connections when the application exits, ensuring resources are freed and preventing potential issues. This addresses a previous oversight where these connections weren't properly closed, potentially leading to resource leaks or unexpected behavior.

Even though we free up the adb connection we don't close the server because other programs may be using the connection.
MikeRatcliffe added a commit to MikeRatcliffe/sidenoder that referenced this issue Sep 17, 2024
Fixes VRPirates#34

Cleanly closes `adb` and `rclone` connections when the application exits, ensuring resources are freed and preventing potential issues. This addresses a previous oversight where these connections weren't properly closed, potentially leading to resource leaks or unexpected behavior.

Even though we free up the adb connection we don't close the server because other programs may be using the connection.
MikeRatcliffe added a commit to MikeRatcliffe/sidenoder that referenced this issue Sep 17, 2024
fix: Properly close `adb` and `rclone` on exit

Fixes VRPirates#34

Cleanly closes `adb` and `rclone` connections when the application exits, ensuring resources are freed and preventing potential issues. This addresses a previous oversight where these connections weren't properly closed, potentially leading to resource leaks or unexpected behavior.

Even though we free up the adb connection we don't close the server because other programs may be using the connection.
MikeRatcliffe added a commit to MikeRatcliffe/sidenoder that referenced this issue Sep 18, 2024
Fixes VRPirates#34

Cleanly closes `adb` and `rclone` connections when the application exits, ensuring resources are freed and preventing potential issues. This addresses a previous oversight where these connections weren't properly closed, potentially leading to resource leaks or unexpected behavior.

Even though we free up the adb connection we don't close the server because other programs may be using the connection.
MikeRatcliffe added a commit to MikeRatcliffe/sidenoder that referenced this issue Sep 30, 2024
Fixes VRPirates#34

Cleanly closes `adb` and `rclone` connections when the application
exits, ensuring resources are freed and preventing potential issues.
This addresses a previous oversight where these connections weren't
properly closed, potentially leading to resource leaks and unexpected
behavior.

Even though we free up the adb connection we don't close the server
because other programs may be using the connection.

The changes introduce a `destroy()` function in `tools.js` that handles
the cleanup. This function is called when the application receives the
"will-quit" event, ensuring that resources are freed before the
application terminates.

This change enhances the application's reliability and stability by
preventing resource leaks and ensuring a clean exit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant