pleroma

commit: 7e99d0619d02835fab66134f14dd99fb4c313d26
parent 0fbec6b532330e86da9b396f31f9d5dd04990a9e
Author: Mark Felder <feld@feld.me>
Date:   Mon, 12 Feb 2024 17:25:02 -0500

Force more frequent full_sweep GC runs on the Websocket processes

Websocket processes seem to be the primary culprit for Binary memory allocation bloat.

Diffstat:
A
changelog.d/memleak.fix
1
+
M
lib/pleroma/web/endpoint.ex
6
++++--

2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/changelog.d/memleak.fix b/changelog.d/memleak.fix
@@ -0,0 +1 @@
+Fix a memory leak caused by Websocket connections that would not enter a state where a full garbage collection run could be triggered.
diff --git a/lib/pleroma/web/endpoint.ex b/lib/pleroma/web/endpoint.ex
@@ -14,7 +14,8 @@ defmodule Pleroma.Web.Endpoint do
     websocket: [
       path: "/",
       compress: false,
-      error_handler: {Pleroma.Web.MastodonAPI.WebsocketHandler, :handle_error, []}
+      error_handler: {Pleroma.Web.MastodonAPI.WebsocketHandler, :handle_error, []},
+      fullsweep_after: 20
     ]
   )
 
@@ -27,7 +28,8 @@ defmodule Pleroma.Web.Endpoint do
       ],
       timeout: 60_000,
       transport_log: false,
-      compress: false
+      compress: false,
+      fullsweep_after: 20
     ],
     longpoll: false
   )