ASSERT (4.2.0-3 chrome.exe) link.c:1767

_From [jannew...@google.com](https://code.google.com/u/112145647090500735738/) on March 11, 2014 12:46:10_

For the Summary, please follow the guidelines at https://code.google.com/p/dynamorio/wiki/BugReporting and use one of the CRASH, APP CRASH, HANG, or ASSERT keywords What version of DynamoRIO are you using? 4.2.0-3 Does the latest build from http://build.chromium.org/p/client.dynamorio/builds/ solve the problem? No. What operating system version are you running on? Win7 x64. What application are you running? Chrome.exe from http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?path=Win/133517/ Is your application 32-bit or 64-bit? 32-bit. How are you running the application under DynamoRIO? drrun -debug -max_bb_instrs 128 -c $my_client$ -- $chrome.exe$ What happens when you run without any client? What happens when you run with debug build ("-debug" flag to drrun/drconfig/drinject)? What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? Is this an application crash, a DynamoRIO crash, a DynamoRIO assert, or a hang (see https://code.google.com/p/dynamorio/wiki/BugReporting and set the title appropriately)? Please provide any additional information below. Since this is a custom tool, I cannot provide the source for my client, but I attached a stack trace as generated by Windbg.

**Attachment:** [screenshot.png stack_trace.txt](http://code.google.com/p/dynamorio/issues/detail?id=1387)

_Original issue: http://code.google.com/p/dynamorio/issues/detail?id=1387_

Start with link.c:1767 and the attached WinDbg stack trace, then review the reported drrun invocation using Chrome.exe, -debug, -max_bb_instrs 128, and the custom client. Done means reproducing the assertion or narrowing it to the reported setup and identifying the relevant failure cause.

Written by the indexing model from the issue text.