New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ASSERT alloc.c:3166 "!pt->expect_lib_to_fail || pt->alloc_base == NULL (free() success unexpected)" with -no_check_uninitialized #534
Comments
From timurrrr@google.com on August 02, 2011 06:37:39 Looks like the crash is flaky and not always reproduces with --gtest_filter="CertVerifierTest.CacheHit" FTR, when I first saw the crash I was running net_unittests w/o gtest_filter and it crashed on the CacheHit test. |
From timurrrr@google.com on October 14, 2011 08:45:58 could be caused by issue #533 ? Labels: Hotlist-Chrome |
From bruen...@google.com on July 10, 2012 14:16:34 ** TODO shorter repro, but of course may be different underlying bug: create_process.exe hello.exe % ~/drmemory/git/build_x86_dbg/bin/drmemory.exe -dr_debug -dr_ops "-stderr_mask 15" -batch -dr d:/derek/dr/git/exports -light -- bin32/create_process.exe d:/derek/dr/test/hello.exe 4 |
From bruen...@google.com on August 28, 2012 14:22:26 I ran unit_tests on CertVerifierTest.CacheHit and the whole set of tests on win7 and I can't repro this. the hello.exe repro also shows no bug. I'm going to assume this was fixed by the issue #962 fix. Status: Duplicate |
From timurrrr@google.com on August 02, 2011 09:19:01
[ r438 /Win7]
observed on Chromium net_unittests --gtest_filter="CertVerifierTest.CacheHit"
ChildEBP RetAddr
00 170f8ae4 72042f5c ntdll!NtRaiseHardError+0x12
01 170f8b28 7202ca8b dynamorio!nt_messagebox+0x7c [dynamorio\core\win32\ntdll.c @ 3296]
02 170f9b70 1011eb4c dynamorio!dr_messagebox+0x8b [dynamorio\core\x86\instrument.c @ 3134]
03 170f9b7c 1011eb93 drmemorylib!wait_for_user+0xc [common\utils.c @ 82]
04 170f9bc8 100c0555 drmemorylib!drmemory_abort+0x33 [common\utils.c @ 110]
05 170f9c04 100bf882 drmemorylib!handle_free_post+0x495 [common\alloc.c @ 3166]
06 170f9eb0 1b6f6b2c drmemorylib!handle_alloc_post+0x1512 [common\alloc.c @ 4418]
WARNING: Frame IP not in any known module. Following frames may be wrong.
07 003ef65c 019b61be <Unloaded_???CFGMGR32.dll>+0x1b696b2b
08 003ef6a0 01986532 net_unittests!_free_base+0xee [f:\dd\vctools\crt_bld\self_x86\crt\src\free.c @ 109]
09 003ef6b0 01986180 net_unittests!_free_dbg_nolock+0x382 [f:\dd\vctools\crt_bld\self_x86\crt\src\dbgheap.c @ 1384]
0a 003ef6e8 01970d59 net_unittests!_free_dbg+0x50 [f:\dd\vctools\crt_bld\self_x86\crt\src\dbgheap.c @ 1258]
0b 003ef724 01629eb0 net_unittests!operator delete+0xb9 [f:\dd\vctools\crt_bld\self_x86\crt\src\dbgdel.cpp @ 54]
0c 003ef734 01132fb6 net_unittests!base::internal::InvokerStorage1<...>::`scalar deleting destructor'+0x20
0d 003ef74c 01132f3c net_unittests!base::RefCountedThreadSafe<...>::DeleteInternal+0x26 [base\memory\ref_counted.h @ 149]
0e 003ef758 011312f9 net_unittests!base::DefaultRefCountedThreadSafeTraitsbase::internal::InvokerStorageBase::Destruct+0xc [base\memory\ref_counted.h @ 115]
0f 003ef76c 0113086c net_unittests!base::RefCountedThreadSafe<...> >::Release+0x39 [base\memory\ref_counted.h @ 143]
10 003ef778 0164011f net_unittests!scoped_refptrbase::internal::InvokerStorageBase::~scoped_refptr<...>+0x1c [base\memory\ref_counted.h @ 242]
11 003ef784 0143f4af net_unittests!base::internal::CallbackBase::~CallbackBase+0xf [base\callback_internal.cc @ 33]
12 003ef790 01623faf net_unittests!base::Callback<void __cdecl(void)>::~Callback<void __cdecl(void)>+0xf
13 003ef79c 01623e19 net_unittests!MessageLoop::PendingTask::~PendingTask+0xf [base\message_loop.cc @ 756]
Before the crash I've seen a few reports like this which look a bit strange:
UNADDRESSABLE ACCESS: 0x000046dc-0x000046dd 1 byte(s) within 0x000046dc-0x000046e0 [xref issue #533 ? - see address]
#1 RtlGetCurrentProcessorNumberEx ntdll.dll+0x341de
#2 RtlInterlockedFlushSList ntdll.dll+0x32c59
#3 RtlInterlockedFlushSList ntdll.dll+0x32bf2
#4 LocalReAlloc KERNELBASE.dll+0x151c5
#5 I_CryptGetTls CRYPT32.dll+0xa4bb
#6 I_CertSyncStore CRYPT32.dll+0x209d6
#7 I_CertSyncStore CRYPT32.dll+0x20952
#8 I_CertSyncStore CRYPT32.dll+0x20912
#9 I_CryptFindLruEntryData CRYPT32.dll+0x23adc
#10 CryptMsgClose CRYPT32.dll+0x205b5
#11 CertControlStore CRYPT32.dll+0x11642
#12 I_CertSyncStore CRYPT32.dll+0x20899
#13 I_CertSyncStore CRYPT32.dll+0x2082c
#14 I_CertSyncStore CRYPT32.dll+0x20899
#15 I_CertSyncStore CRYPT32.dll+0x2082c
#16 I_CertSyncStore CRYPT32.dll+0x20899
#17 I_CertSyncStore CRYPT32.dll+0x2082c
#18 I_CertSyncStore CRYPT32.dll+0x20899
#19 I_CertSyncStore CRYPT32.dll+0x2082c
#20 I_CryptFindLruEntryData CRYPT32.dll+0x240c2
#21 I_CryptFindLruEntryData CRYPT32.dll+0x236c0
#22 CertCreateCertificateChainEngine CRYPT32.dll+0x24232
#23 net::TestRootCerts::GetChainEngine net\base\test_root_certs_win.cc:189
#24 net::X509Certificate::VerifyInternal net\base\x509_certificate_win.cc:741
#25 net::X509Certificate::Verify net\base\x509_certificate.cc:601
#26 net::CertVerifierWorker::Run net\base\cert_verifier.cc:157
UNADDRESSABLE ACCESS: 0x0410d744-0x0410d745 1 byte(s) within 0x0410d744-0x0410d748 [why only 1 byte?!]
Note: next higher malloc: 0x0410db60-0x0410db80
Note: prev lower malloc: 0x0410d610-0x0410d630
#1 _free_dbg_nolock crt\src\dbgheap.c:1323
#2 _free_dbg crt\src\dbgheap.c:1258
#3 operator delete crt\src\dbgdel.cpp:54
...
INVALID HEAP ARGUMENT: RtlFreeHeap 0x0410d730
#1 HeapFree KERNEL32.dll+0x114cb
#2 _free_base crt\src\free.c:109
#3 _free_dbg_nolock crt\src\dbgheap.c:1384
#4 _free_dbg crt\src\dbgheap.c:1258
#5 operator delete crt\src\dbgdel.cpp:54
Original issue: http://code.google.com/p/drmemory/issues/detail?id=534
The text was updated successfully, but these errors were encountered: