You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IIRC we discussed that this isn't a dup, the stacks here are pretty different despite both having userenv.dll!CreateEnvironmentBlock in them.
This popped up again on the bot: http://build.chromium.org/p/client.drmemory/builders/win-7_x64-drm/builds/2011 Our existing suppression isn't good enough because by default we only go 11 frames deep. Without tracing further, I don't see a way to suppress this precisely. I also generally expect that 11 frames is not enough for most users. Can we increase the default to 15 or more?
From rnk@google.com on January 19, 2012 12:38:12
Chromium has the following code in base::LaunchProcess for launching a process as another user:
IMO it's pretty clear that environment_block is not leaked, yet we get these reports: http://build.chromium.org/p/chromium.fyi/builders/Windows%20Tests%20%28DrMemory%20full%29/builds/514/steps/memory%20test%3A%20base/logs/stdio
Dr.MError#4
: LEAK 28 direct bytes 0x005aa1d0-0x005aa1ec + 840 indirect bytesDr.M# 0 RPCRT4.dll!? +0x0 (0x75f00636 <RPCRT4.dll+0x10636>)Dr.M# 1 RPCRT4.dll!? +0x0 (0x75f00610 <RPCRT4.dll+0x10610>)Dr.M# 2 RPCRT4.dll!I_RpcAllocateDr.M# 3 RPCRT4.dll!NDRCContextMarshallDr.M# 4 RPCRT4.dll!NDRCContextMarshallDr.M# 5 RPCRT4.dll!NDRCContextMarshallDr.M# 6 RPCRT4.dll!NdrClientInitializeDr.M# 7 RPCRT4.dll!? +0x0 (0x75fa015a <RPCRT4.dll+0xb015a>)Dr.M# 8 SspiCli.dll!? +0x0 (0x75333478 <SspiCli.dll+0x23478>)Dr.M# 9 SspiCli.dll!CredUnmarshalTargetInfoDr.M#10
SspiCli.dll!? +0x0 (0x75329b7a <SspiCli.dll+0x19b7a>)Dr.M#11
SspiCli.dll!? +0x0 (0x75329d21 <SspiCli.dll+0x19d21>)Dr.M#12
SspiCli.dll!? +0x0 (0x75329d71 <SspiCli.dll+0x19d71>)Dr.M#13
SspiCli.dll!CredUnmarshalTargetInfoDr.M#14
SspiCli.dll!? +0x0 (0x7532a448 <SspiCli.dll+0x1a448>)Dr.M#15
profapi.dll!? +0x0 (0x7502324f <profapi.dll+0x324f>)Dr.M#16
profapi.dll!? +0x0 (0x750231e8 <profapi.dll+0x31e8>)Dr.M#17
profapi.dll!? +0x0 (0x75022e40 <profapi.dll+0x2e40>)Dr.M#18
profapi.dll!? +0x0 (0x7502225c <profapi.dll+0x225c>)Dr.M#19
USERENV.dll!CreateEnvironmentBlockDr.M#20
base::LaunchProcess [base\process_util_win.cc:316]Dr.M#21
ProcessUtilTest_LaunchAsUser_Test::TestBody [base\process_util_unittest.cc:418]Dr.M#22
testing::internal::HandleExceptionsInMethodIfSupportedtesting::Test,void [testing\gtest\src\gtest.cc:2145]Dr.MDr.MError#5
: LEAK 16 direct bytes 0x005b8a08-0x005b8a18 + 0 indirect bytesDr.M# 0 RPCRT4.dll!? +0x0 (0x75f00636 <RPCRT4.dll+0x10636>)Dr.M# 1 RPCRT4.dll!? +0x0 (0x75f00610 <RPCRT4.dll+0x10610>)Dr.M# 2 RPCRT4.dll!RpcBindingFreeDr.M# 3 RPCRT4.dll!NdrConformantVaryingArrayBufferSizeDr.M# 4 RPCRT4.dll!RpcBindingSetAuthInfoExWDr.M# 5 RPCRT4.dll!RpcBindingSetAuthInfoExWDr.M# 6 RPCRT4.dll!RpcBindingFreeDr.M# 7 RPCRT4.dll!RpcBindingSetAuthInfoExWDr.M# 8 RPCRT4.dll!I_RpcBindingCopyDr.M# 9 RPCRT4.dll!NDRCContextMarshallDr.M#10
RPCRT4.dll!NDRCContextMarshallDr.M#11
RPCRT4.dll!NDRCContextMarshallDr.M#12
RPCRT4.dll!NdrClientInitializeDr.M#13
RPCRT4.dll!? +0x0 (0x75fa015a <RPCRT4.dll+0xb015a>)Dr.M#14
SspiCli.dll!? +0x0 (0x75333478 <SspiCli.dll+0x23478>)Dr.M#15
SspiCli.dll!CredUnmarshalTargetInfoDr.M#16
SspiCli.dll!? +0x0 (0x75329b7a <SspiCli.dll+0x19b7a>)Dr.M#17
SspiCli.dll!? +0x0 (0x75329d21 <SspiCli.dll+0x19d21>)Dr.M#18
SspiCli.dll!? +0x0 (0x75329d71 <SspiCli.dll+0x19d71>)Dr.M#19
SspiCli.dll!CredUnmarshalTargetInfoDr.M#20
SspiCli.dll!? +0x0 (0x7532a448 <SspiCli.dll+0x1a448>)Dr.M#21
profapi.dll!? +0x0 (0x7502324f <profapi.dll+0x324f>)Dr.M#22
profapi.dll!? +0x0 (0x750231e8 <profapi.dll+0x31e8>)Dr.M#23
profapi.dll!? +0x0 (0x75022e40 <profapi.dll+0x2e40>)Dr.M#24
profapi.dll!? +0x0 (0x7502225c <profapi.dll+0x225c>)Dr.M#25
USERENV.dll!CreateEnvironmentBlockDr.M#26
base::LaunchProcess [base\process_util_win.cc:316]Dr.M#27
ProcessUtilTest_LaunchAsUser_Test::TestBody [base\process_util_unittest.cc:418]Dr.M#28
testing::internal::HandleExceptionsInMethodIfSupportedtesting::Test,void [testing\gtest\src\gtest.cc:2145]Dr.MDr.MError#6
: LEAK 2 direct bytes 0x005bd2f0-0x005bd2f2 + 0 indirect bytesDr.M# 0 RPCRT4.dll!? +0x0 (0x75f00636 <RPCRT4.dll+0x10636>)Dr.M# 1 RPCRT4.dll!? +0x0 (0x75f00610 <RPCRT4.dll+0x10610>)Dr.M# 2 RPCRT4.dll!RpcBindingFree +0x62a (0x75f0ae96 <RPCRT4.dll+0x1ae96>)Dr.M# 3 RPCRT4.dll!NdrConformantVaryingArrayBufferSize +0x755 (0x75f10efe <RPCRT4.dll+0x20efe>)Dr.M# 4 RPCRT4.dll!RpcBindingSetAuthInfoExW +0x620 (0x75f11cbe <RPCRT4.dll+0x21cbe>)Dr.M# 5 RPCRT4.dll!RpcBindingSetAuthInfoExW +0x5b7 (0x75f11c55 <RPCRT4.dll+0x21c55>)Dr.M# 6 RPCRT4.dll!RpcBindingFree +0xf0f (0x75f0b77b <RPCRT4.dll+0x1b77b>)Dr.M# 7 RPCRT4.dll!RpcBindingSetAuthInfoExW +0x57f (0x75f11c1d <RPCRT4.dll+0x21c1d>)Dr.M# 8 RPCRT4.dll!I_RpcBindingCopy +0x35 (0x75f0b98b <RPCRT4.dll+0x1b98b>)Dr.M# 9 RPCRT4.dll!NDRCContextMarshall +0x21d (0x75f08314 <RPCRT4.dll+0x18314>)Dr.M#10
RPCRT4.dll!NDRCContextMarshall +0x18b (0x75f08282 <RPCRT4.dll+0x18282>)Dr.M#11
RPCRT4.dll!NDRCContextMarshall +0x150 (0x75f08247 <RPCRT4.dll+0x18247>)Dr.M#12
RPCRT4.dll!NdrClientInitialize +0x124 (0x75f07116 <RPCRT4.dll+0x17116>)Dr.M#13
RPCRT4.dll!? +0x0 (0x75fa015a <RPCRT4.dll+0xb015a>)Dr.M#14
SspiCli.dll!? +0x0 (0x75333478 <SspiCli.dll+0x23478>)Dr.M#15
SspiCli.dll!CredUnmarshalTargetInfo +0x156f (0x75324cb4 <SspiCli.dll+0x14cb4>)Dr.M#16
SspiCli.dll!? +0x0 (0x75329b7a <SspiCli.dll+0x19b7a>)Dr.M#17
SspiCli.dll!? +0x0 (0x75329d21 <SspiCli.dll+0x19d21>)Dr.M#18
SspiCli.dll!? +0x0 (0x75329d71 <SspiCli.dll+0x19d71>)Dr.M#19
SspiCli.dll!CredUnmarshalTargetInfo +0x288f (0x75325fd4 <SspiCli.dll+0x15fd4>)Dr.M#20
SspiCli.dll!? +0x0 (0x7532a448 <SspiCli.dll+0x1a448>)Dr.M#21
profapi.dll!? +0x0 (0x7502324f <profapi.dll+0x324f>)Dr.M#22
profapi.dll!? ...Original issue: http://code.google.com/p/drmemory/issues/detail?id=757
The text was updated successfully, but these errors were encountered: