mitmdump: use a dummy state object

Most of the mitmdump memory leak turns out to be due to our leaky handling of
the state object. Since mitmdump doesn't actually use the state object, we can
replace it with a shell.

1 files changed, 1 insertions, 8 deletions

diff --git a/mitmproxy/dump.py b/mitmproxy/dump.py
index 0e942eac..92dce37b 100644
--- a/mitmproxy/dump.py
+++ b/mitmproxy/dump.py
@@ -35,7 +35,7 @@ class Options(options.Options):
 class DumpMaster(flow.FlowMaster):
 
     def __init__(self, server, options):
-        flow.FlowMaster.__init__(self, options, server, flow.State())
+        flow.FlowMaster.__init__(self, options, server, flow.DummyState())
         self.has_errored = False
         self.addons.add(*builtins.default_addons())
         self.addons.add(dumper.Dumper())
@@ -82,13 +82,6 @@ class DumpMaster(flow.FlowMaster):
         if e.level == "error":
             self.has_errored = True
 
-    @controller.handler
-    def request(self, f):
-        f = super(DumpMaster, self).request(f)
-        if f:
-            self.state.delete_flow(f)
-        return f
-
     def run(self):  # pragma: no cover
         if self.options.rfile and not self.options.keepserving:
             self.addons.done()