I attached VS2017 to the process as it crashed and tried to copy the the exception details to the clipboard.  VS2017 reported

OpenClipboard Failed (Exception from HRESULT: 0x800401D0 (CLIPBRD_E_CANT_OPEN))

Deleted: ChromeCrash.png 39.7 KB

	ChromeCrash.png 39.7 KB View Download

Unable to reproduce the issue on Windows 10 using chrome reported version-70.0.3538.77,latest stable-70.0.3538.102 & latest canary-72.0.3608.0 as per steps mentioned in C#0.

No crash observed after step 3.Please check the issue on latest chrome versions & let us know your observations on the same.

Find the attached screencast for reference.

Deleted: 904256-win-Unable to repro.mp4 3.8 MB

	904256-win-Unable to repro.mp4 3.8 MB View Download

[Stability Sheriff] I wasn't able to repro this on Windows 10, Chrome 72.0.3608.4 (64-bit).

Some quick web searching suggests that other applications can get exclusive access to the clipboard through Win32 APIs and cause problems like this.  I recommend looking at other software on your system and seeing if disabling/uninstalling it makes the crash go away.

I've been able to reproduce when building Chromium from source.  There is an access violation down in the bowels of the clipboard libraries which is not being handled.

It fails calling SetClipboardData.

(from clipboard_win.cc, lines 907-913)
void ClipboardWin::WriteToClipboard(unsigned int format, HANDLE handle) {
  DCHECK(clipboard_owner_->hwnd() != NULL);
  if (handle && !::SetClipboardData(format, handle)) {
    DCHECK(ERROR_CLIPBOARD_NOT_OPEN != GetLastError());
    FreeData(format, handle);
  }
}

(from the Debug console window in VC2017)
Exception thrown at 0x00007FFCB53C56B8 in chrome.exe: Microsoft C++ exception: IPCException at memory location 0x000000AB8E5F94D0.
Exception thrown at 0x00007FFCB53C56B8 in chrome.exe: Microsoft C++ exception: vontu_dlp::DLPException at memory location 0x000000AB8E5F9670.
Exception thrown at 0x00007FFCB8AFAB5D (ntdll.dll) in chrome.exe: 0xC0000005: Access violation writing location 0x00000000C00000C8.

Going up the call stack, all the local variables look okay.  The immediate caller is ClipboardWin::WriteText and the text variable contains the information I copied from the URL.

Are you able to assist, I've got no idea where to start looking for the culprit?

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the issue on windows 10 using chrome#70.0.3538.110. No crash is seen on copying the url at login screen.

@Slaneyrw: Could you please check by updating chrome to latest stable #70.0.3538.110. Is this crash is consistently reproducible?

Thanks!

Might be helpful to find where the regression occurred via the bisect script:
https://www.chromium.org/developers/bisect-builds-py