This error message...
ERROR:broker_win.cc(55)] Error reading broker pipe: The pipe has been ended. (0x6D)
...implies that the pipe is broken as if the browser side has been closed.
This error is defined in broker_win.cc within the Chromium code repository as follows:
Channel::MessagePtr WaitForBrokerMessage(PlatformHandle platform_handle,
BrokerMessageType expected_type) {
char buffer[kMaxBrokerMessageSize];
DWORD bytes_read = 0;
BOOL result = ::ReadFile(platform_handle.handle, buffer,
kMaxBrokerMessageSize, &bytes_read, nullptr);
if (!result) {
// The pipe may be broken if the browser side has been closed, e.g. during
// browser shutdown. In that case the ReadFile call will fail and we
// shouldn't continue waiting.
PLOG(ERROR) << "Error reading broker pipe";
return nullptr;
}
The main reason you see this error is because the ChromeDriver controlled Chrome browser gets detected and the navigation gets blocked.
Solution
As a solution you may need to configure the ChromeDriver / Chrome with certain configurations so Selenium driven Chrome Browsing Context doesn't get detected.
References
You can find a couple of relevant detailed discussions in:
tl; dr
Broken pipe error selenium webdriver, when there is a gap between commands?