Oneric 4f44d08816 [TEST] Avoid accumulating stale data in websockets ... For some but not all instances (likely depending on usage patterns) those [i’m guessing, to be tested] process end up accumulating stale binary data in such a way it’s not included into young garbage collection cycles. At the same time, full cycles are barely ever triggered making it seem like a memory leak. To avoid this, make full sweeps more frequent for only the affected processes. TODO: actually test this theory + fix ref: https://www.erlang.org/doc/man/erlang#ghlink-process_flag-2-idp226 https://blog.guzman.codes/using-phoenix-channels-high-memory-usage-save-money-with-erlfullsweepafter (showed up in search results and inspired this) https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4060 (different patch due to different socket implementation)		2024-04-04 17:32:05 +02:00
..
mix	Ensure that spoof-inserted does not time out	2024-03-30 12:55:22 +00:00
phoenix/transports/web_socket	Migrate to phoenix 1.7 (#626)	2023-08-15 10:22:18 +00:00
pleroma	[TEST] Avoid accumulating stale data in websockets	2024-04-04 17:32:05 +02:00