[Bug]: Memory leak after macOS sleep — t3code consumes 63GB RAM on wake, making system unusable

[muhammadhaad]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

Build, CI, or release tooling

Steps to reproduce

Description

After leaving t3code running overnight with my MacBook in sleep mode (lid closed),
the app consumed ~63GB of RAM on wake, making the entire system unresponsive and
requiring a force restart to recover.

Steps to Reproduce

1. Open t3code and use it normally during the day
2. Close the MacBook lid (sleep mode) without quitting t3code or any other apps
3. Open the lid the next day
4. Observe the system becomes sluggish / unresponsive

Note: I was unable to reliably reproduce this on demand, but it has occurred
on two consecutive days under the same conditions. I also could not capture
screenshots due to the system being unresponsive.

Additional Context

• No screenshots available (system was unresponsive during the event)
• Issue reproduced on two separate days under similar conditions
• All other applications remained open during sleep (no manual app close before sleeping)
• Force restart was the only recovery method

Expected behavior

t3code should either release memory while the system is sleeping, or remain within
normal memory bounds after wake — consistent with its pre-sleep usage.

Actual behavior

t3code was observed consuming ~63GB of RAM after wake (checked via Activity Monitor
after force restart and replication on day 2). The system was completely unusable —
login was not possible on day 1 and required a force restart.

Impact

Major degradation or frequent failure

Version or commit

T3 Code v0.0.24

Environment

Field	Value
OS	macOS Tahoe 26.5
Machine	MacBook Pro M1 Pro
RAM	64GB
Storage	512GB SSD
t3code ver	Alpha (latest available)

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response