From bruen...@google.com on January 20, 2011 15:59:21

• TODO TOFILE False possible leak in gdi32!CreateDCW

one of a few Chromium leaks https://code.google.com/p/chromium/issues/detail?id=68307 reported:

POSSIBLE LEAK 440 direct bytes 0x01d42e78-0x01d43030 + 0 indirect bytes
...
#18 0x77f1be50 CreateDCW GDI32.dll
#19 0x005d0f73 printing::PrintingContextWin::AllocateContext printing\printing_context_win.cc:467
#20 0x0041aca1 PrintDlgExMock printing\printing_context_win_unittest.cc:65

doesn't look like a real leak. looks like CreateDCW returns a device
context handle and the allocation is kept internal, so not surprising that
there's some funny business, but need to analyze further.

Original issue: http://code.google.com/p/drmemory/issues/detail?id=274