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

[Bug]: Very high resource usage when child process is terminated #246

Open
ilarikokko opened this issue Jan 4, 2025 · 0 comments
Open
Labels
bug Something isn't working

Comments

@ilarikokko
Copy link

GridPlayer version

0.5.3

What OS are you using?

Windows

OS Version / Linux distribution

Windows 10

What distribution channel are you using? [LINUX ONLY]

None

Bug description

I came across this bug when I started making StreamDeck macros for GridPlayer management.

RESOURCE USAGE WHEN THE APPLICATION IS RUNNING
running

Stream Deck has an option to kill the application (I don't know what shutdown command StreamDeck uses underneath the surface) and when using this I noticed that even though the application window closes, the other process of the application stays on and starts consuming a lot of resources, especially CPU usage increases exponentially.

AFTER KILLING THE PROCESS
after_killing

I started investigating the issue and it seems that the problem in question is caused by the fact that if only one of the processes is killed, the application goes into some kind of error state and starts consuming resources. I was able to reproduce this when I ended only the second process from the "Details" view of Task Manager. I don't know which process is causing the problem when it is killed, but with enough effort, when you kill the right one, the other one starts consuming resources.

DETAILS VIEW
details

I also tried the AutoHotKey command Process, Close, GridPlayer.exe, which causes the same problem. Only one of the child processes is closed. However, the AutoHotKey command WinClose, GridPlayer kills both child processes and the problem does not occur.

When using the command taskkill /IM GridPlayer.exe directly from the command line, this command kills both processes, no problem.

POWERSHELL COMMAND
image

I don't know enough about this to say whether the problem is because Windows is handling the processes strangely, whether the application's close commands are stupid because they don't close all processes, or whether the problem is directly in the GridPlayer application. However, the problem may also occur to others who try to use ready-made programs, such as StreamDeck, to close this application.

Log excerpt

No response

@ilarikokko ilarikokko added the bug Something isn't working label Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant