It's actually crashing

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%283%29/builds/9871/steps/memory%20test%3A%20content/logs/stdio

[----------] 9 tests from FileSystemDirURLRequestJobTest
[ RUN      ] FileSystemDirURLRequestJobTest.DirectoryListing
<Application E:\b\build\slave\chromium-dbg-win-drmemory-full-3\build\src\out\Release\content_unittests.exe (984).  Dr. Memory internal crash at PC 0x65eadb63.  Please report this at http://drmemory.org/issues.  Program aborted.
0xc0000005 0x00000000 0x65eadb63 0x65eadb63 0x00000001 0x00000000
Base: 0x65e20000
Registers: eax=0x65f046e8 ebx=0x00000000 ecx=0x00000075 edx=0x00000000
	esi=0x2cd52988 edi=0x2cd52988 esp=0x1e46edb4 ebp=0x00000000
	eflags=0x000
1.10.0-2-(Mar  7 2016 23:05:56) win61

I filed a bug:

https://github.com/DynamoRIO/drmemory/issues/1870

 Issue 595490  has been merged into this issue.

 Issue 594808  has been merged into this issue.

I have a local fix for this and will update the Cr bits soon.

 Issue 594614  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/236662f34717e607aaa942eef49853cd1be21f33

commit 236662f34717e607aaa942eef49853cd1be21f33
Author: bruening <bruening@chromium.org>
Date: Sun Mar 20 04:44:32 2016

Update Dr. Memory to 1.10.16880 (0xe299f42)

TBR=zhaoqin@chromium.org, oshima@chromium.org
BUG= 440500 , 595792 , 594614 , 595158 
NOTRY=true

Review URL: https://codereview.chromium.org/1820683002

Cr-Commit-Position: refs/heads/master@{#382214}

[modify] https://crrev.com/236662f34717e607aaa942eef49853cd1be21f33/third_party/drmemory/README.chromium
[modify] https://crrev.com/236662f34717e607aaa942eef49853cd1be21f33/third_party/drmemory/drmemory-windows-sfx.exe.sha1

 Issue 594785  has been merged into this issue.

 Issue 594618  has been merged into this issue.

 Issue 595156  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fa7a7747d6f9cb16cda4e8caf946ef2e26cc894b

commit fa7a7747d6f9cb16cda4e8caf946ef2e26cc894b
Author: bruening <bruening@chromium.org>
Date: Sun Mar 20 20:23:02 2016

Remove unused VS2015 realloc heap mismatch suppression.

The suppression was never hit on the bots, and I cannot reproduce it
locally even running Dr. Memory builds prior to the several VS2015 fixes.
If with the latest Dr. Memory it happens again in some environments, we
would prefer to address it at the Dr. Memory level rather than with a
Chromium suppression as it is general enough to affect external users.

BUG= 595792 
TBR=brucedawson@chromium.org
NOTRY=true

Review URL: https://codereview.chromium.org/1819753002

Cr-Commit-Position: refs/heads/master@{#382226}

[modify] https://crrev.com/fa7a7747d6f9cb16cda4e8caf946ef2e26cc894b/tools/valgrind/drmemory/suppressions.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/81b119c2386ef476253fca400e865c4813aa0139

commit 81b119c2386ef476253fca400e865c4813aa0139
Author: bruening <bruening@chromium.org>
Date: Sun Mar 20 20:25:44 2016

Remove Dr. Memory suppression that is no longer needed.

We strongly suspect that this handle leak is caused by the  issue 595792 
crash and that the suppression is not needed.

BUG= 595156 , 595792 
TBR=oshima
NOTRY=true

Review URL: https://codereview.chromium.org/1821503002

Cr-Commit-Position: refs/heads/master@{#382230}

[modify] https://crrev.com/81b119c2386ef476253fca400e865c4813aa0139/tools/valgrind/drmemory/suppressions_full.txt