Aw, Snap! crash when rendering large paginated datasets in Opera

Goal: identify the maximum number of DOM nodes that can be safely rendered in Opera when using client‑side pagination with virtual scrolling before the renderer triggers an 'Aw, Snap!' crash.

Constraints include the Opera version, available system RAM, whether the built‑in ad blocker is enabled, Turbo mode status, and GPU‑related flags such as --disable-gpu or --enable-features=VizDisplayCompositor. The exact threshold is known to vary, and layout thrashing from rapid row insertion/removal can further reduce the safe limit.

Questions: What is the approximate DOM‑node threshold for Opera Desktop 100 on an 8 GB RAM machine with default settings? How does enabling the ad blocker change that threshold? Does disabling GPU acceleration raise or lower the limit before the crash occurs?