Possible leak false pos from WS2_32.dll!gethostbyname

[derekbruening]

From [email protected] on January 12, 2012 14:27:29

Report from chromium full bot on remoting_unittests.exe: http://build.chromium.org/p/chromium.fyi/builders/Windows%20Tests%20%28DrMemory%20full%29/builds/333/steps/memory%20test%3A%20remoting/logs/stdio POSSIBLE LEAK 40 direct bytes 0x03570978-0x035709a0 + 0 indirect bytes
#0 fwpuclnt.dll!FwpmFreeMemory0 +0x64 (0x73416373 <fwpuclnt.dll+0x6373>)
#1 fwpuclnt.dll!FwpmFreeMemory0 +0x33 (0x73416343 <fwpuclnt.dll+0x6343>)
#2 fwpuclnt.dll!FwpmFreeMemory0 +0x92 (0x734163a2 <fwpuclnt.dll+0x63a2>)
#3 RPCRT4.dll!NdrCorrelationPass +0x2b3 (0x75f08a68 <RPCRT4.dll+0x18a68>)
#4 RPCRT4.dll!NdrConformantVaryingArrayUnmarshall +0x290 (0x75f0c3a4 <RPCRT4.dll+0x1c3a4>)
#5 RPCRT4.dll!NdrPointerUnmarshall +0x2f (0x75f0915c <RPCRT4.dll+0x1915c>)
#6 RPCRT4.dll!NdrSimpleStructBufferSize +0x417 (0x75f090df <RPCRT4.dll+0x190df>)
#7 RPCRT4.dll!NdrPointerUnmarshall +0x2f (0x75f0915c <RPCRT4.dll+0x1915c>)
#8 RPCRT4.dll!NdrClientInitialize +0x124 (0x75f07116 <RPCRT4.dll+0x17116>)
#9 RPCRT4.dll!? +0x0 (0x75fa015a <RPCRT4.dll+0xb015a>)
#10 fwpuclnt.dll!FwpmEngineGetOption0 +0x69 (0x7341a832 <fwpuclnt.dll+0xa832>)
#11 fwpuclnt.dll!FwpmEngineGetOption0 +0x38 (0x7341a801 <fwpuclnt.dll+0xa801>)
#12 fwpuclnt.dll!FwpmEngineOpen0 +0x523 (0x7341a659 <fwpuclnt.dll+0xa659>)
#13 fwpuclnt.dll!FwpmProcessNameResolutionEvent0 +0x73 (0x73412e71 <fwpuclnt.dll+0x2e71>)
#14 fwpuclnt.dll!NamespaceCallout +0x71 (0x73412dcb <fwpuclnt.dll+0x2dcb>)
#15 WS2_32.dll!WSAEnumNameSpaceProvidersExW +0x1b2 (0x7590a234 <WS2_32.dll+0x1a234>)
#16 WS2_32.dll!WSASetServiceW +0x2050 (0x75901657 <WS2_32.dll+0x11657>)
#17 WS2_32.dll!gethostbyname +0xe6 (0x7590775a <WS2_32.dll+0x1775a>)
#18 talk_base::SafeGetHostByName [third_party\libjingle\source\talk\base\nethelpers.cc:123]
#19 talk_base::SocketAddress::GetLocalIPs [third_party\libjingle\source\talk\base\socketaddress.cc:454]
#20 talk_base::SocketAddress::IsLocalIP [third_party\libjingle\source\talk\base\socketaddress.cc:223]
#21 cricket::Transport::VerifyCandidate [third_party\libjingle\source\talk\p2p\base\transport.cc:261]
#22 cricket::Session::OnRemoteCandidates [third_party\libjingle\source\talk\p2p\base\session.cc:591]
#23 cricket::Session::OnTransportInfoMessage [third_party\libjingle\source\talk\p2p\base\session.cc:936]
#24 cricket::Session::OnIncomingMessage [third_party\libjingle\source\talk\p2p\base\session.cc:735]
#25 cricket::SessionManager::OnIncomingMessage [third_party\libjingle\source\talk\p2p\base\sessionmanager.cc:162]
#26 remoting::JingleSignalingConnector::OnSignalStrategyIncomingStanza [remoting\jingle_glue\jingle_signaling_connector.cc:58]
#27 remoting::FakeSignalStrategy::DeliverIncomingMessages [remoting\jingle_glue\fake_signal_strategy.cc:110]
#28 base::internal::RunnableAdapter<void (__thiscall remoting::FakeSignalStrategy::*)(void)>::Run [base\bind_internal.h:132]

This is kind of a bizarre report. I'm filing here to investigate later. Because it's a possible leak, I'm guessing this object is still reachable, and this isn't a real leak.

Original issue: http://code.google.com/p/drmemory/issues/detail?id=749