Andrew, do you know who could take a look at this leak (i guess this one is real)
I looked at the LSan log, and all of the leaks are indirect, except for one where the allocation happens here: mozilla::net::nsHttpTransaction::SetSecurityCallbacks(nsIInterfaceRequestor*) /home/worker/workspace/build/src/netwerk/protocol/http/nsHttpTransaction.cpp:511 Honza, do you know who might know about these security callbacks? Thanks.
Component: General → Networking: HTTP
Flags: needinfo?(continuation) → needinfo?(honzab.moz)
This hasn't been seen in the last week, so maybe it was fixed.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
Aha! the leak is from here: https://dxr.mozilla.org/mozilla-central/rev/27311156637f9b5d4504373967e01c4241902ae7/netwerk/protocol/http/nsHttpTransaction.cpp#511 Looks like the dispatch fails. Is this is a shutdown leak?
(In reply to Honza Bambas (:mayhemer) from comment #5) > Looks like the dispatch fails. Is this is a shutdown leak? LeakSanitizer reports blocks of memory that are alive at shutdown, but not reachable from the stack.
3 failures in 831 pushes (0.004 failures/push) were associated with this bug in the last 7 days. Repository breakdown: * mozilla-inbound: 1 * mozilla-central: 1 * autoland: 1 Platform breakdown: * linux64: 3 For more details, see: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1358128&startday=2018-02-26&endday=2018-03-04&tree=all
2 failures in 747 pushes (0.003 failures/push) were associated with this bug in the last 7 days. Repository breakdown: * mozilla-central: 2 Platform breakdown: * linux64: 2 For more details, see: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1358128&startday=2018-03-05&endday=2018-03-11&tree=all
You need to log in before you can comment on or make changes to this bug.