Streaming.stop failing and causes current stream to not save a video

Related app/team name: Insights Capture

Issue Description:
Sometimes when the streaming.stop api is called the api fails and we receive an unknown onStreamingError not a streaming.stop error.

The error is causing the recorded video to not save.

In in_game.html.58.log after “match end detected”, we call streaming.stop(), but we receive an onStreamingError.

In Overwolf_06-09-22_18-26-49.Game.html, corresponding to the in_game.html.58.log we see both a StopStreaming success and a HandleStreamingStoppedError.

Can you reproduce it (exact steps to reproduce):
We haven’t been able to reproduce it internally, but users run into this issue after a few recordings. The logs show the same thing. After 3 - 4 streams successfully started and stopped, the next one fails to stop.

Impact for my app: had 5 people in the last week run into this problem

Do you currently have a workaround?
We made a change to reset our internal state to allow users to start a new stream. This assumes OBS itself is not in an unrecoverable state and can start a new stream though.

However, the video for the stream that failed to stop properly is still lost.

Please reproduce and attach a zip package of your OW client logs
Please mention the time of the event so we can find it easily in the logs (2.0 MB)

Times are mentioned above, but they happen in many of the in_game.html logs.

We will try to reproduce this issue and keep you updated as it progresses!

do have anothor logs?
becasue the related obs log is missing… (probebly already deleted)

Hi Oded,

The attached logs has the unknown error inside of “in_game.html.35.log”. The time stamp is below in the screenshots. (4.3 MB)

i think we found the issus,
we will release a possible fix in the up coming version (201)

1 Like