Skip to main content

Browser & Memory Troubleshooting (Chrome, Edge, "Aw, Snap!")

The full guide for fixing the "Aw, Snap!" crashes, mic auto-adjust, and Hardware Acceleration in Chrome and Edge.

This guide consolidates the three most common fixes: Hardware Acceleration, mic auto-adjust, and the hard refresh.


EnrollHere's Browser Support Stance

  • Chrome β€” officially supported and recommended for all production dialing.

  • Edge β€” secondary support. Most things work, but we don't fix Edge-only bugs first.

  • Safari / Firefox β€” not officially supported for the dialer.

πŸ“Œ If an agent is having problems on Edge, the first thing to try is switching to Chrome β€” except for the "Aw, Snap!" / out-of-memory issue below, which now affects both browsers (see next section).


"Aw, Snap!" / Out of Memory (Chrome and Edge)

A recent Chrome update combined with a concurrent Windows 11 patch is causing Chrome tabs to crash with "Aw, Snap! Out of Memory." Microsoft has since shipped a parallel update for Edge, so Edge users are seeing the same crash β€” typically presented as "This page is having a problem" or a blank/black tab. It hits power users hardest (multiple monitors, many tabs, 8 GB RAM laptops).

⚠️ Because both browsers are affected, switching browsers will not resolve this specific crash. The fix is the Hardware Acceleration toggle below.

Recovery Steps

  1. Close other tabs and unused apps to free RAM. The dialer should have a dedicated, focused window.

  2. Disable Hardware Acceleration:

    • Chrome: open chrome://settings/system in the URL bar.

    • Edge: open edge://settings/system in the URL bar.

    • Find "Use graphics acceleration when available" (or search "Hardware Acceleration" in the Settings search bar to jump there).

    • Toggle it off.

    • Restart the browser.

  3. Clear the cache: Ctrl + Shift + Delete β†’ "Cached images and files" β†’ Clear data.

  4. Update the browser to the latest version: chrome://settings/help or edge://settings/help.

  5. Restart the computer if the crashes persist.

βœ… Disabling Hardware Acceleration is currently the most reliable single fix for this crash on either browser.


Mic Auto-Adjustment (Chrome & Edge)

Chrome and Edge will auto-lower your microphone gain mid-call if they detect "loud" input β€” which kills audibility for the consumer. See the full fix in Fixing Microphone Volume Auto-Adjustment in Edge & Chrome.

Short version: disable the WebRTC auto-gain flag and lock the mic level in Windows Sound Settings.


When in Doubt β€” Hard Refresh

  1. Windows: Ctrl + Shift + R, or Ctrl + F5.

  2. Mac: Cmd + Shift + R.

A hard refresh resolves a surprising amount: missing UI tabs, stale dispo sets, the AI Agent Training panel not appearing, and stuck queue state. See Troubleshooting Tip: Perform a Hard Refresh.


Hardware Recommendations

  • 16 GB RAM minimum for power users (multiple tabs, monitoring, dashboards open). 8 GB is the floor and will struggle.

  • Wired headset preferred over Bluetooth.

  • Wired ethernet preferred over Wi-Fi for stationary agents.


When to Escalate

Open a support ticket if:

  • "Aw, Snap!" / out-of-memory crashes persist after disabling Hardware Acceleration, clearing cache, and updating the browser.

  • Crashes are happening to multiple agents in your agency at the same time (likely an outage or release issue).

  • A specific browser version is reproducibly causing crashes β€” we'll log a Linear ticket.

Include: browser name and version (chrome://settings/help or edge://settings/help), OS version, RAM, and the exact time of one or two crashes.


πŸ“Œ Tip

Run all agents on Chrome with Hardware Acceleration off by default right now. The crash pattern is widespread enough that proactively flipping the toggle β€” on either browser β€” prevents tickets you'd otherwise see this week.

Did this answer your question?