Log states of JobController in Net MemoryDumpProvider

net/http/http_stream_factory_impl_job.cc

Index: net/http/http_stream_factory_impl_job.cc
diff --git a/net/http/http_stream_factory_impl_job.cc b/net/http/http_stream_factory_impl_job.cc
index 2cd3bcbe0b6c7cf73b0129896405537a9a92cfcb..f72c40ab9b5f1e751b038f98e0f19d00d43198e3 100644
--- a/net/http/http_stream_factory_impl_job.cc
+++ b/net/http/http_stream_factory_impl_job.cc
@@ -46,6 +46,7 @@
 #include "net/socket/socks_client_socket_pool.h"
 #include "net/socket/ssl_client_socket.h"
 #include "net/socket/ssl_client_socket_pool.h"
+#include "net/socket/stream_socket.h"
 #include "net/spdy/bidirectional_stream_spdy_impl.h"
 #include "net/spdy/spdy_http_stream.h"
 #include "net/spdy/spdy_protocol.h"
@@ -334,6 +335,13 @@ bool HttpStreamFactoryImpl::Job::using_spdy() const {
   return using_spdy_;
 }
 
+size_t HttpStreamFactoryImpl::Job::EstimateMemoryUsage() const {
+  StreamSocket::SocketMemoryStats stats;
+  if (connection_)
+    connection_->DumpMemoryStats(&stats);
+  return stats.total_size;

[ssid, 2017/01/18 23:51:52]

So, this does not include
stream_, websocket_stream_, bidirectional_stream_impl_.
Are these not important?

[xunjieli, 2017/01/19 14:50:42]

The lifetime of a Job is very short. Once connection is established, stream_ and
websocket_stream_, bidirectional_stream_impl_ are also released to the caller
(usually HttpNetworkTransaction), and Job is destroyed.
Is there an easy way to estimate their size?

[ssid, 2017/01/20 20:20:23]

Okay this is good for now. If we see a lot of difference between the reported
memory and actual usage, lets come back to this issue.

+}
+
 const SSLConfig& HttpStreamFactoryImpl::Job::server_ssl_config() const {
   return server_ssl_config_;
 }