Thanks for checking the console and recording a video. That OTEL error (OTLPExporterError: Bad Request, “Trace spans collection is not enabled”) confirms there’s a telemetry leak running in the background that uses memory. Every rejected span gets buffered and is never cleared, so the renderer hits the 4 GB limit faster.
This is a separate bug from the general OOM issue, and others have reported it too: Renderer OOM crash: OTEL exporter leaks memory when trace spans rejected (400)
There’s no workaround for the OTEL leak itself yet, but rotating chats more often will help you hit the limit less often.