Skip to content

Race condition between closing and disposing of NamedPipeServerStream causes ObjectDisposedException occasionaly #570

@techtel-pstevens

Description

@techtel-pstevens

Often I get this exception:

---> System.ObjectDisposedException: Cannot access a closed pipe.
at System.IO.Pipes.NamedPipeServerStream.CheckDisconnectOperations()
at System.IO.Pipes.NamedPipeServerStream.Disconnect()
at FFMpegCore.Arguments.PipeArgument.During(CancellationToken cancellationToken)
at FFMpegCore.FFMpegArguments.During(CancellationToken cancellationToken)
at FFMpegCore.FFMpegArgumentProcessor.Process(ProcessArguments processArguments, CancellationTokenSource cancellationTokenSource)
at FFMpegCore.FFMpegArgumentProcessor.ProcessAsynchronously(Boolean throwOnError, FFOptions ffMpegOptions)

On close observation, is it due to the race condition between closing and disposing of NamedPipeServerStream in PipeArgument class.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions