[Bug 18067] Large blocks not reported properly to valgrind by RtlAllocateHeap

http://bugs.winehq.org/show_bug.cgi?id=18067

--- Comment #3 from Austin English   2009-04-17 11:44:32 ---
(In reply to comment #2)
> Patch committed, but Rob pointed out a related problem on wine-devel, let's
> keep this bug open for the moment.

http://www.winehq.org/pipermail/wine-devel/2009-April/074890.html

2009/4/15 Dan Kegel <dank at kegel.com>:
> Two chromium unit tests reported phony errors
> when run on wine on valgrind because
> RtlAllocateHeap sometimes returned an
> allocation without notifying valgrind about it.

RtlReAllocateHeap is also missing valgrind notifications for the large
block paths. It also appears that the function leaks memory in the
realloc small -> large path.