ASSERT common/alloc.c:2185: !pt->expect_lib_to_fail || pt->alloc_base == NULL (free() success unexpected) about drmemory HOT 5 CLOSED

From [email protected] on October 27, 2010 07:20:44

Today we've moved our Chromium bots and the new DrM bot is Vista (AFAIK)
and it has started hitting this assert very often: http://build.chromium.org/p/chromium.fyi/builders/Windows%20Tests%20(DrMemory)/builds/130/steps/memory%20test:%20printing/logs/stdio ...
:::Dr.Memory::: ASSERT FAILURE (thread 3152): C:\drmemory-build\drmemory\common\alloc.c:2185: !pt->expect_lib_to_fail || pt->alloc_base == NULL (free() success unexpected)

Summary: ASSERT common/alloc.c:2185: !pt->expect_lib_to_fail || pt->alloc_base == NULL (free() success unexpected)
Labels: -Priority-Medium Priority-High

from drmemory.

From [email protected] on October 27, 2010 07:41:14

(this is as of r64 / r436 since I couldn't build newer DrM yet)

btw, other tests on Vista hang silently - could be related
(see logs longer than 1200s http://build.chromium.org/p/chromium.fyi/builders/Windows%20Tests%20(DrMemory)/builds/130 )

from drmemory.

From [email protected] on February 11, 2011 12:58:07

I'm seeing this assert on any GUI app's exit on win7. looks like there it's an early alloc from the AV sw and the heap walk doesn't think it's legit.

from drmemory.

From [email protected] on February 14, 2011 16:30:31

the win7 exit-time assert is for different reason: issue #295 the one here is more closely related to issue #51 where the debug CRT should be disabled

from drmemory.

From [email protected] on February 24, 2011 21:15:58

This issue was closed by revision r190 .

Status: Fixed

from drmemory.