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
I am encountering an issue with using FFmpeg on a server. During unit tests or in the event of an application crash, the FFmpeg processes that are created sometimes are not canceled using the CancellationToken. These two issues describe the problem in detail:
It is unfortunate (maybe by design) that there is no direct way to access the FFmpeg processes. Being able to store the processes somewhere would have been a convenient solution to clean up residual processes when necessary.
Thank you for your assistance and suggestions on this matter.
Best regards,
The text was updated successfully, but these errors were encountered:
Hello,
I am encountering an issue with using FFmpeg on a server. During unit tests or in the event of an application crash, the FFmpeg processes that are created sometimes are not canceled using the CancellationToken. These two issues describe the problem in detail:
Issue #333
Issue #468
It is unfortunate (maybe by design) that there is no direct way to access the FFmpeg processes. Being able to store the processes somewhere would have been a convenient solution to clean up residual processes when necessary.
Thank you for your assistance and suggestions on this matter.
Best regards,
The text was updated successfully, but these errors were encountered: