You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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
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
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
The text was updated successfully, but these errors were encountered:
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
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
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
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
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
The text was updated successfully, but these errors were encountered: