Free Memory Test

A memory test verifies the reliability, data integrity, and addressability of memory blocks under active computational workloads. In a web browser, a memory test exercises the JavaScript runtime's memory allocation engine by requesting large typed arrays (Uint8Array), populating them with known bit patterns, and reading them back to check for allocation failures or memory corruption.

The test divides your selected target workload into controlled chunks (such as 64 MB). For each chunk, an ArrayBuffer is allocated, filled with deterministic patterns (e.g. alternating 0xAA/0x55 bits), and verified. Continuous stress passes re-verify these buffers while maintaining a live performance graph and measuring memory operations.

Web browsers are sandboxed for security. A web page cannot address physical RAM directly, read memory controller registers, or bypass the operating system kernel's virtual memory translation. While a browser cannot test raw physical memory traces, it can thoroughly test browser-accessible allocation capacity and memory pressure resilience.

Physical RAM refers to the physical DDR4/DDR5 DIMM chips installed on your motherboard. Browser memory refers to the virtual memory pages allocated to your browser tab process by the operating system, subject to browser tab ceilings, heap limits, and OS pagefile swap mechanics.

This test measures the browser's ability to allocate, write, retain, and read back memory buffers without throwing RangeError: Array buffer allocation failed. It tests the stability of your browser's memory management pipeline and confirms data integrity across the allocated block spectrum.

Allocation fails when the requested buffer exceeds the browser tab's virtual memory cap (often 2 GB to 4 GB on 64-bit systems), when physical RAM and system pagefiles are exhausted, or when memory fragmentation prevents allocating a contiguous memory buffer.

For quick browser sanity checks, 256 MB or 512 MB is ideal. For modern desktop systems with 8 GB to 32 GB of RAM, running a 1 GB or 2 GB test provides a rigorous memory workload without triggering operating system paging stutter.

W3C privacy standards restrict web pages from inspecting exact hardware details. The navigator.deviceMemory API only provides coarse power-of-two approximations capped at 8 GB to prevent cross-site device fingerprinting.

For suspected physical RAM failure, blue screens (BSOD), or kernel panics, boot into a dedicated hardware diagnostic tool such as MemTest86, MemTest86+, or the built-in Windows Memory Diagnostic. Dedicated bootable utilities test every physical memory cell without operating system overhead.