On Fri, 5 Apr 2024 at 23:59, Henrik Grubbström (Lysator) @ Pike (-) developers forum 10353@lyskom.lysator.liu.se wrote:
Is there a better way to handle this than simply forcing garbage collection every request?
The best way is to break the cycle before dropping the object on the floor (or to not introduce it to begin with) or destruct the problematic objects explicitly.
There's no cycles in my code, and this phenomenon doesn't happen with a non-SSL connection, so I'm guessing it's something to do with encryption.
To identify the cycles you may want to log the cycles detected by the gc; take a look at base_server/roxen.pike:reinstall_gc_callbacks().
Thanks, will investigate further.
ChrisA