Closed Bug 1285699 Opened 8 years ago Closed 7 years ago

Intermittent LeakSanitizer | leak at PL_strdup, mozilla::net::nsSocketTransport::Init, mozilla::net::nsSocketTransportService::CreateRoutedTransport, mozilla::net::nsHttpConnectionMgr::nsHalfOpenSocket::SetupStreams

Categories

(Core :: Networking, defect, P3)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: bulk-close-intermittents, intermittent-failure, memory-leak, Whiteboard: [necko-backlog])

Keywords: mlk
Assignee: nobody → mcmanus
Whiteboard: [necko-active]
Assignee: mcmanus → nobody
Whiteboard: [necko-active] → [necko-backlog]
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
>Indirect leak of 144 byte(s) in 1 object(s) allocated from:
>    #0 0x4bb9ec in malloc /builds/slave/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:64:3
>    #1 0x4ecf0d in moz_xmalloc /home/worker/workspace/build/src/memory/mozalloc/mozalloc.cpp:83:17
>    #2 0x7f976934295c in operator new /home/worker/workspace/build/src/obj-firefox/dist/include/mozilla/mozalloc.h:194:12
>    #3 0x7f976934295c in nsDNSService::AsyncResolveExtendedNative(nsACString const&, unsigned int, nsACString const&, nsIDNSListener*, nsIEventTarget*, mozilla::OriginAttributes const&, nsICancelable**) /home/worker/workspace/build/src/netwerk/dns/nsDNSService2.cpp:856
>    #4 0x7f976926ad58 in mozilla::net::nsSocketTransport::ResolveHost() /home/worker/workspace/build/src/netwerk/base/nsSocketTransport2.cpp:1147:15
>    #5 0x7f9769272acb in mozilla::net::nsSocketTransport::OnSocketEvent(unsigned int, nsresult, nsISupports*) /home/worker>/workspace/build/src/netwerk/base/nsSocketTransport2.cpp:2067:30

This should be the root object that causing this leakage. Looks like there is an unresolved nsDNSAsyncRequest kept the nsSocketTransport and nsHalfOpenSocket object.

Since this bug is closed maybe we should file a new bug for tracking it.
You need to log in before you can comment on or make changes to this bug.