diff options
Diffstat (limited to 'meta-openbmc-mods/meta-common/recipes-phosphor/interfaces/bmcweb/0009-Workaround-Fix-memory-leak.patch')
-rw-r--r-- | meta-openbmc-mods/meta-common/recipes-phosphor/interfaces/bmcweb/0009-Workaround-Fix-memory-leak.patch | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/meta-openbmc-mods/meta-common/recipes-phosphor/interfaces/bmcweb/0009-Workaround-Fix-memory-leak.patch b/meta-openbmc-mods/meta-common/recipes-phosphor/interfaces/bmcweb/0009-Workaround-Fix-memory-leak.patch new file mode 100644 index 000000000..90905762b --- /dev/null +++ b/meta-openbmc-mods/meta-common/recipes-phosphor/interfaces/bmcweb/0009-Workaround-Fix-memory-leak.patch @@ -0,0 +1,33 @@ +From f43d6ba7e32565a7881949070bd25cb13f50ebf7 Mon Sep 17 00:00:00 2001 +From: James Feist <james.feist@linux.intel.com> +Date: Thu, 27 Aug 2020 13:56:52 -0700 +Subject: [PATCH 1/1] Workaround: Fix memory leak + +Req caputures self not allowing the connection to +be freed. There is discussion in upstream about a +real fix, this should be kept downstream only. + +Tested: Sent 1000 connections, saw no VSZ increase + +Change-Id: I63440abbe0882ffe228395b5d3bc869f10048ddc +Signed-off-by: James Feist <james.feist@linux.intel.com> +--- + http/http_connection.h | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/http/http_connection.h b/http/http_connection.h +index 109a272..393c2e7 100644 +--- a/http/http_connection.h ++++ b/http/http_connection.h +@@ -422,6 +422,8 @@ class Connection : + { + adaptor.close(); + } ++ // HACK TO REMOVE MEMORY LEAK ++ req.reset(); + } + + void completeRequest() +-- +2.17.1 + |