Closed ran-haim closed 1 year ago
Oh, sorry, I didn't monitor the issues page. Most of communication related to this project happens on the project home page.
I updated the debug version that allows to redirect stdout into a file now (all the log lines are flushed immediately). Run it like this from cmd
:
soundkeeper.exe > soundkeeper.log
But it is suspicious that it exits itself. Maybe it crashes somehow? Please check in the Event Viewer > Windows Logs > Application, look for events with Event Type ID = 1000. If there is something related to the Sound Keeper, it would be really helpful to understand where exactly it crashes. Also, the system should create a crash dump in this case, check here how to collect it.
@ran-haim Maybe it was actually freezing and not terminating itself? A potential bug that could cause a deadlock was fixed in the latest v1.3.1. Please check if it helps you.
Most probably it was actually stopping to work because of the deadlock, but the process was still running. So I guess that the issue is fixed in the latest v1.3.1, so I close this ticket.
It seems that sometimes, usually after one day (probably because I close the tv and av) the soundkeeper.exe exists. I wanted to look in the logs, but it seems you only write to stdoutput so I cannot access that. Can you add ability to write to a log file?
thanks.