Error writing to history when broadcasting input to multiple terminals

Environment data

PS version: 6.0.4
PSReadline version: 2.0.0-beta2
OS: Windows 10, Version 1703 (Build 15063.1209)

Steps to reproduce or exception report

1. Open multiple instances of PowerShell in a terminal emulator which supports split panes and broadcasts (e.g.: ConEmu)
2. Open three splits, resulting in four total open panes.
3. Turn on broadcasting (ctrl+shift+G for ConEmu)
4. Enter a command such as ls and press the Enter key.

Expected behavior

The command runs in all panes and no error is thrown

Actual behavior

The command runs in all panes, but errors will be thrown stating that the history file could not be written to because it is being used by another process

[lzybkr]

In theory, the retry logic is already implemented, see here.

Based on the error, it seems like something is holding on to the file handle outside the mutex - so either I’m missing a using statement, or there is a side effect accessing the file that missed.

[sleighsoft]

This also happens when you programmatically open two terminals at the same time. This can be done with the “Terminals Manager” extension of VSCode, for example. You just configure two or more terminals and “Run Terminals” It will then throw Error reading or writing history file 'C:\Users\...\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt': The process cannot access the file 'C:\Users\...\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt' because it is being used by another process.