search

DynamoRIO / drmemory

Memory Debugger for Windows, Linux, Mac, and Android
Other
2.43k stars 262 forks source link

unit_tests reported Dr. Memory errors on windows FYI bot to be investigated #1053

Open derekbruening opened 9 years ago

derekbruening commented 9 years ago

From zhao...@google.com on October 16, 2012 15:00:03

http://build.chromium.org/p/chromium.fyi/builders/Chromium%20Windows%20Unit%20%28DrMemory%29/builds/231

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

derekbruening commented 9 years ago

From zhao...@google.com on October 16, 2012 12:01:25

remoting_unittests

[ RUN ] NegotiatingAuthenticatorTest.SuccessfulAuthHmac Dr.M Dr.M Error #1: INVALID HEAP ARGUMENT: allocated with malloc, freed with operator delete Dr.M # 0 net.dll!ssl3_FinishHandshake [net\third_party\nss\ssl\ssl3con.c:9592] Dr.M # 1 net.dll!ssl3_HandleFinished [net\third_party\nss\ssl\ssl3con.c:9568] Dr.M # 2 net.dll!ssl3_HandleHandshakeMessage [net\third_party\nss\ssl\ssl3con.c:9836] Dr.M # 3 net.dll!ssl3_HandleHandshake [net\third_party\nss\ssl\ssl3con.c:9910] Dr.M # 4 net.dll!ssl3_HandleRecord [net\third_party\nss\ssl\ssl3con.c:10339] Dr.M # 5 net.dll!ssl3_GatherCompleteHandshake [net\third_party\nss\ssl\ssl3gthr.c:393] Dr.M # 6 net.dll!SSL_ForceHandshake [net\third_party\nss\ssl\sslsecur.c:413] Dr.M # 7 net.dll!net::SSLServerSocketNSS::DoHandshake [net\socket\ssl_server_socket_nss.cc:745] Dr.M # 8 net.dll!net::SSLServerSocketNSS::DoHandshakeLoop [net\socket\ssl_server_socket_nss.cc:674] Dr.M # 9 net.dll!net::SSLServerSocketNSS::OnHandshakeIOComplete [net\socket\ssl_server_socket_nss.cc:526] Dr.M #10 net.dll!net::SSLServerSocketNSS::OnRecvComplete [net\socket\ssl_server_socket_nss.cc:511] Dr.M #11 net.dll!net::SSLServerSocketNSS::BufferRecvComplete [net\socket\ssl_server_socket_nss.cc:608] Dr.M #12 net.dll!base::internal::RunnableAdapter<void (__thiscall net::SpdyWebSocketStream::*)(int)>::Run [base\bind_internal.h:190] Dr.M Note: @0:00:03.479 in thread 1652

split to issue #1050

derekbruening commented 9 years ago

From bruen...@google.com on October 16, 2012 14:19:09

I don't see any failed tests at the link in the 1st comment. are these drmem error reports? I'm adjusting this case to make that clear

Summary: unit_tests reported Dr. Memory errors on windows FYI bot to be investigated
Labels: Bug-FalsePositive

derekbruening commented 9 years ago

From zhao...@google.com on October 16, 2012 15:13:09

The link points to a bot tests and many failures not investigated yet, including

memory test: net http://build.chromium.org/p/chromium.fyi/builders/Chromium%20Windows%20Unit%20%28DrMemory%29/builds/231/steps/memory%20test%3A%20net HttpAuthControllerTest.NoExplicitCredentialsAllowed HttpAuthControllerTest.PermanentErrors HttpResponseHeadersTest.NormalizeHeadersBadStatus SpdyProxyClientSocketSpdy2Test.ConnectRedirects SpdyProxyClientSocketSpdy2Test.ConnectWithAuthRequested SpdyProxyClientSocketSpdy2Test.ReadAuthResponseBody SpdyProxyClientSocketSpdy3Test.ConnectRedirects SpdyProxyClientSocketSpdy3Test.ConnectWithAuthRequested SpdyProxyClientSocketSpdy3Test.ReadAuthResponseBody 0644E9A9EB1399A0 07258C1C2B35685D 07E3565C06E55794 41EBEA66C89F8E79 47DDD0621A0D9AEF 5EB32EF0A726C58D 6C9A612A43728727 7B094EA26F5985E4 8F4CB15A11BD3D77 9D2ED4F2381EC1C4 9EA4100647256E49 AC7F9BA06CD699E3 BF210424D509C164 C2960C0A863AB9C4 C9DE6B186772120E D84A599F7C9C36FB DD1FEF472556E100 E80D040D96DA9EB7 EF01AF89DA27345D EF8A7B1FA3BDB0DF

memory test: unit http://build.chromium.org/p/chromium.fyi/builders/Chromium%20Windows%20Unit%20%28DrMemory%29/builds/231/steps/memory%20test%3A%20unit MalwareDetailsTest.HTTPCache 11ED91F95FD27E35 554C171EF2DC8C7D 7C2B7E4A6967F969 93168F3B4CBB74D8 B44ADF4285671A7B C2960C0A863AB9C4 D84A599F7C9C36FB DEB0EF8ABA3BB2A3 F95C3458FB5D79A0

memory test: remoting http://build.chromium.org/p/chromium.fyi/builders/Chromium%20Windows%20Unit%20%28DrMemory%29/builds/231/steps/memory%20test%3A%20remoting 4A56336839A92087

derekbruening commented 9 years ago

From zhao...@google.com on October 16, 2012 15:14:16

[ RUN ] SpdyProxyClientSocketSpdy2Test.ConnectSendsCorrectRequest Dr.M Dr.M Error #1: UNADDRESSABLE ACCESS: reading 0x0318a9a0-0x0318a9a4 4 byte(s) Dr.M # 0 net.dll!std::basic_string<char,std::char_traits,std::allocator >::_Myptr [c:\program files (x86)\microsoft visual studio 10.0\vc\include\xstring:2010] Dr.M # 1 net.dll!net::HttpResponseHeaders::Parse [net\http\http_response_headers.cc:375] Dr.M # 2 net.dll!net::HttpResponseHeaders::HttpResponseHeaders [net\http\http_response_headers.cc:126] Dr.M # 3 net.dll!net::SpdyHeadersToHttpResponse [net\spdy\spdy_http_utils.cc:79] Dr.M # 4 net.dll!net::SpdyProxyClientSocket::OnResponseReceived [net\spdy\spdy_proxy_client_socket.cc:508] Dr.M # 5 net.dll!net::SpdyStream::OnResponseReceived [net\spdy\spdy_stream.cc:415] Dr.M # 6 net.dll!net::SpdySession::Respond [net\spdy\spdy_session.cc:1366] Dr.M # 7 net.dll!net::SpdySession::OnSynReply [net\spdy\spdy_session.cc:1550] Dr.M # 8 net.dll!net::BufferedSpdyFramer::OnControlFrameHeaderData [net\spdy\buffered_spdy_framer.cc:123] Dr.M # 9 net.dll!net::SpdyFramer::ProcessControlFrameHeaderBlock [net\spdy\spdy_framer.cc:914] Dr.M #10 net.dll!net::SpdyFramer::ProcessInput [net\spdy\spdy_framer.cc:330] Dr.M #11 net.dll!net::SpdySession::OnReadComplete [net\spdy\spdy_session.cc:852] Dr.M #12 net.dll!base::internal::RunnableAdapter<void (__thiscall net::DhcpProxyScriptFetcherWin::*)(int)>::Run [base\bind_internal.h:190]

split to issue #1054