Opera GX RAM Limiter overshoot before tab discarding

Issue

Opera GX’s GX Control panel exposes a RAM Limiter slider that sets a soft ceiling for the browser’s main process memory usage. When the limit is reached, the browser is expected to reduce memory consumption by discarding background tabs, pausing media, and throttling JavaScript timers. However, the exact eviction order, timing, and any allowable overshoot are not publicly documented.

Goal

Determine whether the RAM Limiter enforces the configured ceiling strictly or permits a margin of excess before initiating corrective actions, and clarify the conditions that trigger tab discarding.

Unresolved Questions

1. Does the limiter allow a predictable overshoot (e.g., 10–30 %) before discarding background tabs or throttling occurs?
2. What is the eviction order for tabs when the limit is surpassed—does Opera prioritize the most memory‑hungry tabs, the oldest, or those with active media?
3. Is there a configurable delay or threshold that determines when the limiter reacts, and can it be exposed through an API or debugging interface?