drsyms fails to load chrome.exe and chrome.dll symbols in some ui_tests runs #646
Comments
|
From bruen...@google.com on October 26, 2011 14:20:05 sandbox limitations (related to "Error" msgbox DRi#580)? this is --single-process, btw |
|
From rnk@google.com on November 04, 2011 14:15:37 Can you reproduce this after the recent drsyms changes? |
|
From rnk@google.com on November 04, 2011 14:16:01 Owner: rnk@google.com |
|
From bruen...@google.com on March 22, 2012 15:22:00 I'm also seeing some cases of chrome.dll missing symbols but it seems to be nondet. I notice b/c the GDI suppressions suddenly don't match in some tests. WARNING: unable to load symbols for E:\src\chromium\src\build\Debug\chrome.dll at exit of main thread in renderer process, when using symcache (so didn't need syms earlier) most likely this is the same problem as in issue #723 : too late for dbghelp to operate Summary: drsyms fails to load chrome.exe and chrome.dll symbols in some ui_tests runs |
|
From bruen...@google.com on March 26, 2012 07:28:43 another one on prefetch (must be general threads still running when main WARNING: prefetching unaddressable memory 0x037242a0-0x037242a1 0 (0x1e000037)1 chrome.dll!? +0x0 (0x69e1f612 <chrome.dll+0x5ef612>)2 chrome.dll!? +0x0 (0x69e1c439 <chrome.dll+0x5ec439>)3 chrome.dll!? +0x0 (0x69d52905 <chrome.dll+0x522905>) |
|
From bruen...@google.com on April 24, 2014 15:16:00 This is happening again on the MFYI bots: http://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Unit%20%28DrMemory%20full%29%20%284%29/builds/1002/steps/memory%20test%3A%20unit/logs/stdio UNINITIALIZED READ: reading register ecx 0 MSVCR120.dll!sprintf_s +0x5b (0x6d293fa1 <MSVCR120.dll+0x13fa1>)1 MSVCR120.dll!_uncaught_exception +0x953 (0x6d293eca <MSVCR120.dll+0x13eca>)2 MSVCR120.dll!vsnprintf_s_l +0xa4 (0x6d304bec <MSVCR120.dll+0x84bec>)3 MSVCR120.dll!snprintf_s +0x19 (0x6d3038ff <MSVCR120.dll+0x838ff>)4 unit_tests.exe!? +0x0 (0x02aa7348 <unit_tests.exe+0x1a07348>)5 unit_tests.exe!? +0x0 (0x02aa73b6 <unit_tests.exe+0x1a073b6>)6 unit_tests.exe!? +0x0 (0x018a7b40 <unit_tests.exe+0x807b40>)7 unit_tests.exe!? +0x0 (0x018a7eee <unit_tests.exe+0x807eee>)8 unit_tests.exe!? +0x0 (0x018a7fde <unit_tests.exe+0x807fde>)9 unit_tests.exe!? +0x0 (0x011c05f0 <unit_tests.exe+0x1205f0>)#10 unit_tests.exe!? +0x0 (0x018a819f <unit_tests.exe+0x80819f>) That's probably http://crbug.com/64887? But why no syms? OOM? |
|
From bruen...@google.com on April 24, 2014 20:26:39 Also browser_tests.exe: http://build.chromium.org/p/chromium.fyi/builders/Windows%20Browser%20%28DrMemory%20full%29%20%283%29/builds/3537/steps/memory%20test%3A%20browser_tests/logs/stdio UNINITIALIZED READ: reading register eax 0 browser_tests.exe!? +0x0 (0x023e7081 <browser_tests.exe+0x1217081>)1 browser_tests.exe!? +0x0 (0x023e6f65 <browser_tests.exe+0x1216f65>)2 browser_tests.exe!? +0x0 (0x023e3747 <browser_tests.exe+0x1213747>)3 browser_tests.exe!? +0x0 (0x023e33ab <browser_tests.exe+0x12133ab>)4 browser_tests.exe!? +0x0 (0x023e1d80 <browser_tests.exe+0x1211d80>)5 browser_tests.exe!? +0x0 (0x023dfc4d <browser_tests.exe+0x120fc4d>)6 browser_tests.exe!? +0x0 (0x023de703 <browser_tests.exe+0x120e703>)7 browser_tests.exe!? +0x0 (0x023de2b6 <browser_tests.exe+0x120e2b6>)8 browser_tests.exe!? +0x0 (0x01f0d719 <browser_tests.exe+0xd3d719>)9 browser_tests.exe!? +0x0 (0x01ed3cc1 <browser_tests.exe+0xd03cc1>)#10 browser_tests.exe!? +0x0 (0x0189a97a <browser_tests.exe+0x6ca97a>) |
|
From bruen...@google.com on April 24, 2014 20:26:54 Also v8.dll: https://code.google.com/p/chromium/issues/detail?id=364146 |
|
From bruen...@google.com on April 24, 2014 20:37:54 A few weeks ago we hit an issue with the builder bot for Cr MFYI where the unit_tests pdb kept getting bigger and bigger, with this warning: http://build.chromium.org/p/chromium.memory.fyi/builders/Chromium%20Windows%20Builder%20%28DrMemory%29/builds/5329/steps/compile/logs/warnings%20%281%29 LINK : warning LNK4018: too many type indexes in PDB 'E:\b\build\slave\drm-cr\build\src\out\Release\unit_tests.exe.pdb', discarding subsequent type information Xref https://code.google.com/p/chromium/issues/detail?id=366905 -- this same linker bug may explain the unit_tests symbols at least but perhaps not the v8 ones as they are too old |
|
From bruen...@google.com on April 24, 2014 21:59:46 on FYI: http://build.chromium.org/p/chromium.fyi/builders/Windows%20Builder%20%28DrMemory%29/builds/6017/steps/compile/logs/warnings%20%282%29 LINK : warning LNK4018: too many type indexes in PDB 'E:\b\build\slave\drm-cr\build\src\out\Release\unit_tests.exe.pdb', discarding subsequent type information |
From bruen...@google.com on October 26, 2011 17:17:57
this is in the 2nd chrome.exe process running ui_tests AutomatedUITestBase.Home:
looks like Ci#101537, but why aren't the top symbols resolving?
0:000> dds 0x1af1d0
001af1d0 00f6f4a8 chrome!scoped_ptr<_TOKEN_USER>::~scoped_ptr<_TOKEN_USER>+0x8 [c:\src\chromium\src\base\memory\scoped_ptr.h @ 75]
001af1d4 012b8db0
001af1d8 00f62388 chrome!sandbox::GetHandleName+0xd8 [c:\src\chromium\src\sandbox\src\handle_closer.cc @ 198]
001af1dc 012b8ce8
001af1e0 012a6300
001af1e4 012b8db0
001af1e8 00000008
001af1ec 00f5c105 chrome!sandbox::HandleCloserAgent::CloseHandles+0x1a5 [c:\src\chromium\src\sandbox\src\handle_closer_agent.cc @ 111]
001af1f0 00000004
001af1f4 001af258
001af1f8 75ab1809 kernel32!GetCurrentProcessStub
001af1fc 75acd7ca kernel32!TerminateProcessStub
001af200 01059f74 chrome!instance
Error
#1: INVALID HEAP ARGUMENT: allocated with operator new[], freed with operator delete#0 chrome.exe!? +0x0 (0x00f6f4a8 <chrome.exe+0x1f4a8>)
#1 chrome.exe!? +0x0 (0x00f59724 <chrome.exe+0x9724>)
#2 ntdll.dll!RtlNtStatusToDosError+0x36 (0x77ac6224 <ntdll.dll+0x36224>)
#3 chrome.exe!? +0x0 (0x00f597c5 <chrome.exe+0x97c5>)
#4 chrome.dll!RendererMainPlatformDelegate::EnableSandbox+0x33 [c:\src\chromium\src\content\renderer\renderer_main_platform_delegate_win.cc:128](0x6a05cdc4 <chrome.dll+0x91cdc4)
windbg gets them right:
0:000> U 0x00f6f4a8
chrome!scoped_ptr<_TOKEN_USER>::~scoped_ptr<_TOKEN_USER>+0x8 [c:\src\chromium\src\base\memory\scoped_ptr.h @ 75]:
0:000> U 0x00f59724
chrome!`anonymous namespace'::CloseOpenHandles+0x24 [c:\src\chromium\src\sandbox\src\target_services.cc @ 51]:
0:000> U 0x00f597c5
chrome!sandbox::TargetServicesBase::LowerToken+0x75 [c:\src\chromium\src\sandbox\src\target_services.cc @ 86]:
drmem does print this:
WARNING: unable to load symbols for C:\src\chromium\src\build\Release\chrome.exe
xref issue #635 ""
not sure what's going on: out of memory?
Original issue: http://code.google.com/p/drmemory/issues/detail?id=646
The text was updated successfully, but these errors were encountered: