windows: dvr closes or crashes after some hours

[HamBam2]

i noticed that after several hours the cmd which is running the programm is gone after several hours and i need to restart it again.
i did not see any error messages so far.

are there somewhere logs? no crash logs or so on in the windows logs under system or application.

[YamiOdymel]

The CMD window should not close on its own if it was started with the chaturbate-dvr.exe -u xxx command. Normally, it will stop at the point where it crashed, unless it was started by double-clicking.

Currently, the error only appears in the CMD window and is not saved to a file

[HamBam2]

the -u command is not helpful for me, because i can record only one channel if i understand it correct.

what i noticed:

1. sometimes the app crashes when i access the webserver from a different pc and try to add a channel.
2. after a while there are a lot error messages in the cli every 1 or 2 seconds:

[Date] [ERROR] [username] segment #80 written error: invalid argument
[Date] [ERROR] [username] segment #80 written error: invalid argument
[Date] [ERROR] [username] segment #80 written error: invalid argument
and so on...

the complete folder is in the exeption list for the windows defender. so should not an av problem

[YamiOdymel]

the -u command is not helpful for me, because i can record only one channel if i understand it correct.

If you want to record multiple channels, try to run the program without -u argument, and go Web UI to add channels.

The error message is really- weird, everyone has the different issue but I just cant reproduce it 🥲

[HamBam2]

compile a version which creates debuglogs..... if we know which command is invalid it would help a lot.... or even better: implement a loggingfunction which can be configured by the user from 0 = no logs to 10 = debuglogs or so.

[YamiOdymel]

It does have a little -log-level stuff. If you are using Windows CMD, try the following command:

x64_windows_chaturbate-dvr.exe -log-level DEBUG > logs.txt

This command redirects all output from the program into logs.txt.

Make sure to back up logs.txt before re-running the program, as it will be cleared upon execution.