-
Notifications
You must be signed in to change notification settings - Fork 264
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 (browser_tests -unaddr_only) alloc.c:3401: !TEST(MALLOC_VALID, old_e->flags #1081
Comments
From zhao...@google.com on November 06, 2012 09:31:22 The tests actually starts 4 process, and it is the last process produce this callstack. When running it in debug build and attach on windbg, an assertion failure is seen instead: |
From zhao...@google.com on November 06, 2012 09:32:06 0:000> kp |
From bruen...@google.com on November 06, 2012 10:01:26 is this a dup of issue #1066 ? for the assert, what version of drmem is this? is that issue #1072 ? |
From zhao...@google.com on November 06, 2012 11:18:48 The assert is caused in DrM r1104 , and only happens when I attach the debugger. It looks the callstack problem is similar. will merge them. |
From zhao...@google.com on November 06, 2012 11:19:29 Issue 1066 has been merged into this issue. |
From zhao...@google.com on November 06, 2012 14:22:57 For the assert: 0:000> kn ChildEBP RetAddr00 233ed0a0 5a95567e ntdll!NtRaiseHardError+0x12 0:000> .frame 3 0:000> dv 0:000> dt old_e 0:000> dt drmemorylib!e 0x9: MALLOC_VALID | MALLOC_ALLOCATOR_NEW 0:000> .frame 4 0:000> dv 0:000> dt routine 0:000> ?? *(drwrap_context_t *)wrapcxt 0:000> U 0x5abf9c40 0:000> U 0x5abe7db1-5 Looks like a valid memory block [0x11af0d18, 0x11af0d2c] is added twice. |
From zhao...@google.com on November 06, 2012 14:24:04 0:000> dd 11af0d10 |
From bruen...@google.com on November 06, 2012 14:32:06
Can you update the title if this is now just about the assert. What do you mean "when I attach the debugger": when you execute the app under Dr. Memory inside the debugger's control? Or you attach and the debugger's injected thread hits this error? I assume the former as the callstack doesn't look like the injected thread. How long did you run it in the debugger before the assert fired? |
From zhao...@google.com on November 06, 2012 14:59:04 Because it is the 4th browser_tests process cause the problem, I use -msgbox_mask 0xf and attach the windbg to the 4th process is started, and the let it run. It took a short time to hit this assert, saw a lot of illegal instr and access violation. Summary: ASSERT (browser_tests -unaddr_only) alloc.c:3401: !TEST(MALLOC_VALID, old_e->flags |
From zhao...@google.com on November 07, 2012 11:40:04 For useless callstack, the failure to get symbol for skia.dll is because of failure in to open file in load_module. 0:000> kn ChildEBP RetAddr00 17eee23c 128b914a drmemorylib!load_module+0x33 [d:\src\cygwin\home\zhaoqin\workspace\drmemory\drmemory.git\dynamorio\ext\drsyms\drsyms_windows.c @ 283] in load_module 0:000> dt f 0:000> dds esp 0:000> da 183ce024 12c81c38 44 00 3a 00 5c 00 73 00 72 00 63 00 5c 00 63 00 D.:..s.r.c..c. |
From bruen...@google.com on November 07, 2012 11:51:23 Issue 1066 has been merged into this issue. |
From zhao...@google.com on November 07, 2012 11:54:18 issue #1066 will be used for no-sym callstack and this issue will for the assert failure as shown in the title. |
From zhao...@google.com on November 06, 2012 12:29:34
~/Workspace/DrMemory/builds/build_x86_dbg.svn/bin/drmemory.exe -dr_ops "-msgbox_mask 0x1" -suppress ../../tools/valgrind/drmemory/suppressions.txt -callstack_max_frames 40 -unaddr_only -check_gdi -- ./browser_tests.exe --gtest_filter=Canvas2DDisabledTest.Canvas2DDisabled --ui-test-action-timeout=60000000 -ui-test-action-max-timeout=60000000
WARNING: application is missing line number information.
Error
#1
: GDI USAGE ERROR: DC 0xec01266d that contains selected object being deleted#0 system call NtGdiDeleteObjectApp
#1 GDI32.dll!? +0x0 (0x757c58c5 <GDI32.dll+0x158c5>)
#2 skia.dll!? +0x0 (0x05c307b3 <skia.dll+0x607b3>)
#3 skia.dll!? +0x0 (0x05c30687 <skia.dll+0x60687>)
#4 skia.dll!? +0x0 (0x05c3060f <skia.dll+0x6060f>)
#5 skia.dll!? +0x0 (0x05bea4b1 <skia.dll+0x1a4b1>)
#6 skia.dll!? +0x0 (0x05bea3ac <skia.dll+0x1a3ac>)
#7 skia.dll!? +0x0 (0x05c30da0 <skia.dll+0x60da0>)
#8 skia.dll!? +0x0 (0x05c303ad <skia.dll+0x603ad>)
#9 skia.dll!? +0x0 (0x05bea4b1 <skia.dll+0x1a4b1>)
#10 skia.dll!? +0x0 (0x05bea3ac <skia.dll+0x1a3ac>)
#11 skia.dll!? +0x0 (0x05c8f946 <skia.dll+0xbf946>)
#12 skia.dll!? +0x0 (0x05c8f8bf <skia.dll+0xbf8bf>)
#13 skia.dll!? +0x0 (0x05c8f7e5 <skia.dll+0xbf7e5>)
#14 skia.dll!? +0x0 (0x05c8e0b2 <skia.dll+0xbe0b2>)
#15 skia.dll!? +0x0 (0x05c3e2a8 <skia.dll+0x6e2a8>)
#16 surface.dll!? +0x0 (0x0a2f31f0 <surface.dll+0x131f0>)
#17 content.dll!? +0x0 (0x08898fab <content.dll+0x9c8fab>)
#18 content.dll!? +0x0 (0x08891f95 <content.dll+0x9c1f95>)
#19 content.dll!? +0x0 (0x0889085f <content.dll+0x9c085f>)
#20 content.dll!? +0x0 (0x0888e355 <content.dll+0x9be355>)
#21 content.dll!? +0x0 (0x0889aedc <content.dll+0x9caedc>)
#22 content.dll!? +0x0 (0x0888c12c <content.dll+0x9bc12c>)
#23 content.dll!? +0x0 (0x08849921 <content.dll+0x979921>)
#24 content.dll!? +0x0 (0x086b6668 <content.dll+0x7e6668>)
#25 content.dll!? +0x0 (0x086b660b <content.dll+0x7e660b>)
#26 content.dll!? +0x0 (0x084d73ed <content.dll+0x6073ed>)
#27 ipc.dll!? +0x0 (0x0a28a702 <ipc.dll+0xa702>)
#28 ipc.dll!? +0x0 (0x0a28f006 <ipc.dll+0xf006>)
#29 ipc.dll!? +0x0 (0x0a28ed27 <ipc.dll+0xed27>)
#30 ipc.dll!? +0x0 (0x0a28e8ba <ipc.dll+0xe8ba>)
#31 base.dll!? +0x0 (0x10047b8e <base.dll+0x47b8e>)
#32 base.dll!? +0x0 (0x1009db20 <base.dll+0x9db20>)
#33 base.dll!? +0x0 (0x1009dded <base.dll+0x9dded>)
#34 base.dll!? +0x0 (0x1009ea57 <base.dll+0x9ea57>)
#35 base.dll!? +0x0 (0x100a7fc8 <base.dll+0xa7fc8>)
#36 base.dll!? +0x0 (0x1009d6f3 <base.dll+0x9d6f3>)
#37 base.dll!? +0x0 (0x1009d4a4 <base.dll+0x9d4a4>)
#38 base.dll!? +0x0 (0x100e9222 <base.dll+0xe9222>)
#39 base.dll!? +0x0 (0x1009c96f <base.dll+0x9c96f>)
Note: @0:00:09.451 in thread 6108
Original issue: http://code.google.com/p/drmemory/issues/detail?id=1081
The text was updated successfully, but these errors were encountered: