Forgot to add that I crashed Chrome three separate times to ensure it was not a fluke.

-D

Is your browser configured to report crashes to Google? If so, can you open chrome://crashes and update this report with the "Uploaded Crash Report ID"?

I enabled crash reporting, and crashed Chrome again. Unfortunately none of these crashes are showing up in chrome://crashes.

The first DMP file:
DEFAULT_BUCKET_ID:  NULL_POINTER_READ_IN_CALL

LAST_CONTROL_TRANSFER:  from 0000000072b204f6 to 0000000072b20468

STACK_TEXT:  
00000000`0032e5f0 00000000`72b204f6 : 0000e07a`238bf884 00000000`ea5fc0f2 00000000`0032e708 00000000`72ad20da : msvcr100!_invoke_watson+0x18
00000000`0032e620 00000000`72b20519 : 00000000`00000022 00000000`0032ebe9 00000000`000032b0 00000000`00000000 : msvcr100!_invalid_parameter+0x6e
00000000`0032e660 00000000`72ae69d8 : 0000e07a`238bfb04 00000000`00000000 000007fe`f1ae1470 00000000`000032b0 : msvcr100!_invalid_parameter_noinfo+0x19
00000000`0032e6a0 000007fe`f1a8305d : 00000000`0032ebb0 00000000`00000000 00000000`00000000 00000000`00000101 : msvcr100!wcscpy_s+0x30
00000000`0032e6d0 00000000`0032ebb0 : 00000000`00000000 00000000`00000000 00000000`00000101 00000000`00000000 : clpbm64+0x305d
00000000`0032e6d8 00000000`00000000 : 00000000`00000000 00000000`00000101 00000000`00000000 00000000`000000aa : 0x32ebb0

clpbm64.dll appears to be a Symantec module injected into the process (http://www.shouldiremoveit.com/NYL-AgentInstall64-69207-program.aspx), which calls an API in the runtime library with an illegal parameter.

The dump also shows that EMET is installed, which historically has exhibited some level of compatibility problems with Chrome, although this doesn't look like one of them.

wfh@, question: How do we normally handle crashes due to AV in the security queue?

Kicking into stability queue

Tested this issue on on  Windows-7 using chrome latest stable #59.0.3071.104 & canary #61.0.3115.4  by following steps :

1.Searched for a URL encoded string "https%3A%2F%2Flpages.svb.com%2FEvent-TheAiPoweredEnterprise_VCs_MainLandingPage.html&data=01%7C01%7Cghoyem%40iqt.org%7C144ec98eac7d4a321aca08d4778230c1%7C48f0f988108345a8a724202b255cce64%7C0&sdata=skqj%2Bw53%2FXQ6pEIRs%2BoGNe0j3TcjQ9h0YklfMGTE7ls%3D&reserved=0". 
The search returned results.
2. Highlighted and copy (Using ctrl+c only) the link back out of the search field on the search results page and did not observe any Crash
	
shtychkn@:Please find the screencast and let us know if anything missed here to reproduce the issue.

Thanks..!!

Deleted: 731190.webm 3.1 MB

	731190.webm 3.1 MB View Download

mmanchala:

I was just able to reproduce it in Version 59.0.3071.104 (Official Build) (64-bit)

The versions of software possibly involved:
Symantec DLP 14.5.0.24028
Symantec EndPoint 12.1.7004.6500
EMET 5.5

Deleted: chrome.exe.7076.dmp 4.0 MB

chrome.exe.7076.dmp 4.0 MB Download

Thank you for providing more feedback. Adding requester "mmanchala@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Unable to reproduce the issue on  Windows-7 using chrome latest stable #59.0.3071.104 & canary #61.0.3141.0 by following steps :

1.Searched for a URL encoded string "https%3A%2F%2Flpages.svb.com%2FEvent-TheAiPoweredEnterprise_VCs_MainLandingPage.html&data=01%7C01%7Cghoyem%40iqt.org%7C144ec98eac7d4a321aca08d4778230c1%7C48f0f988108345a8a724202b255cce64%7C0&sdata=skqj%2Bw53%2FXQ6pEIRs%2BoGNe0j3TcjQ9h0YklfMGTE7ls%3D&reserved=0" >> search returned results.
2. Highlighted and copied (Using ctrl+c only) the link back out of the search field on the search results page and did not observe any Crash
	
shtychkn@:Please find the attached screencast and let us know if anything missed here to reproduce the issue.

Thanks..!!

Deleted: 731190.webm 4.2 MB

	731190.webm 4.2 MB View Download

It looks like you covered it. It must be caused by another piece of software that is installed on the system.

Thank you for providing more feedback. Adding requester "rkalavakuntla@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Re #12: To be clear, did you have EMET and Symantec products installed when you confirmed that this didn't repro?

I'm sorry, was that question for me or rkalavakuntla

@elawerence: Yes, I have products installed while confirming..
The versions of software involved:
Symantec DLP 14.5.0.24028
Symantec EndPoint 12.1.7004.6500
EMET 5.5

elawrence@ your query has answered in comment #17, Could you look into it and update the latest info. 

Unfortunately, I don't think there's anything actionable for the Chrome team here, as the crashing code appears to be in the third-party Symantec product.