Chrome Device Memory — Complete Guide

In this tutorial, you'll learn about Chrome Device Memory. We cover key concepts, practical examples, and best practices to help you understand and apply this topic effectively.

Hook

You visit a website that uses navigator.deviceMemory to check your device's RAM. It reports only 1 GB when your system has 16 GB. Or you get "This device does not support memory reporting." Websites are showing "low memory" warnings incorrectly.

The Wrong Way

Spoofing navigator.deviceMemory via Chrome DevTools overrides is fine for testing but does not fix the underlying reporting issue.

// BAD: Overriding in DevTools console
Object.defineProperty(navigator, 'deviceMemory', { get: () => 8 });

Website now thinks you have 8 GB
But only for the current tab — not persistent
Reload the page: back to 1 GB

DevTools overrides are session-only.

The Right Way

Check which Chrome processes are being measured and enable the Device Memory API.

# 1. Check if Device Memory API is available
# Open chrome://version and look for "Device Memory" value

# 2. Check chrome://flags for Device Memory
# chrome://flags → Search: "memory"

# Confirm these flags:
# #enable-experimental-web-platform-features — Default
# #enable-blink-features — (leave empty)

# 3. The Device Memory API is only available in HTTPS pages
# Check if the website uses HTTPS (not HTTP)

# 4. Check if Chrome has enough memory pressure to report
# The API reports the lower of:
# - Actual installed RAM
# - Chrome's process memory limit (for 32-bit Chrome)

# 5. If using 32-bit Chrome on a 64-bit system:
# 32-bit processes are limited to 2-4 GB address space
# Switch to 64-bit Chrome to see full RAM

# 6. Verify in a simple test page
# Open https://googlechrome.github.io/samples/device-memory/

navigator.deviceMemory: 8 GB
device-memory header: 8.0

If the demo shows the correct value, the issue is on the specific website's implementation.

Prevention

• Use 64-bit Chrome on 64-bit operating systems.
• Ensure Chrome is up to date — Device Memory API is supported since Chrome 63.
• The API reports RAM in powers of 2 (0.25, 0.5, 1, 2, 4, 8 GB) — it rounds down.
• Memory reporting is a hint, not an exact measurement.
• Websites should not rely solely on Device Memory for critical functionality.

Common Mistakes with device memory

1. Forgetting deriving (Show, Eq) on custom data types needed for debugging
2. Placing the wildcard pattern first in case expressions, making all subsequent patterns unreachable
3. Using head and tail instead of pattern matching, causing runtime errors on empty lists

These mistakes appear frequently in real-world CHROME code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

DodaTech — memory reporting that reflects your real hardware.