Force more frequent full_sweep GC runs on the Websocket processes

Websocket processes seem to be the primary culprit for Binary memory allocation bloat.
This commit is contained in:
Mark Felder 2024-02-12 17:25:02 -05:00
parent 0fbec6b532
commit 7e99d0619d
2 changed files with 5 additions and 2 deletions

1
changelog.d/memleak.fix Normal file
View File

@ -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.

View File

@ -14,7 +14,8 @@ defmodule Pleroma.Web.Endpoint do
websocket: [ websocket: [
path: "/", path: "/",
compress: false, 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, timeout: 60_000,
transport_log: false, transport_log: false,
compress: false compress: false,
fullsweep_after: 20
], ],
longpoll: false longpoll: false
) )