DeviceTriage
Troubleshooting guide

Why is my browser using so much memory?

Separate normal tab isolation from extensions, runaway pages, memory pressure, and a damaged browser profile.

Review browser and memory signals

Common symptoms

  • Memory use keeps growing after tabs are closed
  • Tabs reload when switching between them
  • The whole device slows down during a browser session

Possible causes

  • Many active tabs, media pages, or complex web applications
  • Extensions running scripts in every tab
  • A page or browser process leaking memory
  • Limited available memory or pressure from other applications

How to diagnose it

  1. Open the browser task manager and sort processes by memory
  2. Restart without restoring every tab, then compare a clean session
  3. Disable extensions in groups and repeat the same workload
  4. Check operating-system memory pressure rather than judging one process number alone

Solutions to try

  1. Close or suspend tabs that are no longer in use
  2. Remove extensions that consume memory without providing value
  3. Update the browser and reproduce the issue in a fresh profile
  4. Reduce simultaneous heavy applications before considering a hardware upgrade

The first 10-minute diagnosis

  1. Record the starting memory state, reproduce the same workload, and observe whether use stabilizes.
  2. Sort the browser task manager by memory to separate tabs, extensions, GPU process, and service workers.
  3. Close one suspected tab and wait briefly; normal caches may be retained while harmful pressure should fall.
  4. Use operating-system memory pressure or swap activity instead of judging one large process number alone.

Decision path by result

Usage stabilizes and the device stays responsiveThe browser may be using isolation and cache normally; monitor pressure, not appearance.
One tab grows continuouslyReproduce without extensions, update the browser, and report the page if growth remains repeatable.
Tabs reload when switchingThe system may be reclaiming memory; reduce active tabs and other heavy applications.
Memory remains high after closing workRestart the browser once, compare a fresh profile, and check for background extensions or service workers.

Platform-specific checks

Windows

Review Memory composition, commit, and paging in Task Manager or Resource Monitor. Available memory and sustained paging are more useful than a single app total.

macOS

Memory Pressure in Activity Monitor is the primary context. Compressed and cached memory can be normal when pressure stays green.

Mobile

Mobile operating systems reclaim background tabs aggressively and rarely expose exact memory. Tab reloads are a stronger user-visible signal than the browser-reported device-memory class.

What not to do first

  • Do not call normal cache or multi-process isolation a leak without repeated growth and impact.
  • Do not use browser-exposed rounded RAM as exact installed or free memory.
  • Do not buy more RAM before identifying whether one extension, page, or unrelated application causes the pressure.

When to move beyond a browser test

  • Report a repeatable page-specific leak with browser version, clean-profile result, and growth over time.
  • Use operating-system diagnostics if memory errors, crashes, or swap pressure affect multiple applications.

Last technical review: 2026-09-01

Frequently asked questions

Is high browser memory use always a leak?

No. Modern browsers isolate tabs and cache data for speed. The stronger warning sign is memory that grows continuously, causes reloads, or does not fall after the workload ends.

Can DeviceTriage see exact free RAM?

No. Browsers may expose only a rounded memory class. Use the operating-system task manager for exact current usage.