Bug / Performance Issue

The WebView renderer process (tauri://localhost) consumes around 914 MB of RAM, making Terax's total memory footprint approximately 1 GB when all subprocesses are counted.

Process Breakdown (from Activity Monitor)

Environment

• macOS (Apple Silicon)
• Physical RAM: 16 GB
• Terax version: (latest as of 2026-05-14)

Impact

On a 16 GB machine, Terax alone consumes ~6% of total RAM. With swap already at 12+ GB due to other apps, this adds significant memory pressure.

Expected

A terminal emulator should ideally use well under 200 MB total. Even feature-rich ones like iTerm2 or Ghostty stay under 350 MB. The WebView layer seems to be the main culprit — it may be loading too many resources, not releasing memory between sessions, or keeping unused WebKit processes alive.

Suggestions

• Investigate WebView memory leaks (detached DOM nodes, uncleaned event listeners, large in-memory caches)
• Consider lazy-loading features or unloading inactive tab WebViews
• Profile with Safari Web Inspector → Terax WebView to identify heap allocations
• Benchmark memory after opening 1 vs 5 vs 10 tabs to check if it scales linearly

Happy to provide more profiling data if needed.