Signals · hardware · counted, not scored by the rubric
Script memory limit
performance.memory.jsHeapSizeLimit: the most memory the JavaScript engine will use for one page, in bytes.
Rubric 1.0.0 does not print a prior for this value. The population still compares it, so the box beside this text counts how many of the devices these sites have read share yours.
How a page reads it
A non-standard Chromium property. Firefox and Safari do not have it, so for them the value is empty, which is a group of its own.
Why it splits browsers apart
The limit is set from the device memory and the browser build, so it splits Chromium browsers along lines similar to device memory, with extra steps for 32-bit builds and memory-saving modes.
What moves it
Installing more memory, switching between 32-bit and 64-bit builds, or some command-line flags.
What moving it costs
A device memory value that does not fit the heap limit is an easy cross-check, and few spoofers set both.
How the count is made
Your value is compared with the latest reading of every device the eight sites read in the last 365 days, this browser's own rows left out. The share is (devices sharing it + 1) ÷ (population + 1), and the bits are −log₂ of that. Why the counts sit beside the priors and are never added to them.
Questions about script memory limit
- Why is this value empty in my browser?
- Only Chromium browsers expose performance.memory. Firefox and Safari do not report it, and that absence is itself a shared value.
- Can a page see how much memory I am using?
- Chromium also reports the current heap size, but that changes from moment to moment. This page counts only the limit, which stays put.
In the same group
Next
Graphics vendor: The unmasked WebGL vendor, for example Google Inc. (Apple) or Google Inc. (NVIDIA).
Where the pens move
A value patched in the page is a patched value. Set in the engine, it is just a value.
Engine level, not JS level. Donut Browser spoofs through CDP injection in its Wayfern Chromium fork, so the value a page reads is the value the engine reports — there is no patched accessor to catch.
It refuses to contradict itself. A profile whose proxy exit geography, time zone or language disagrees with its fingerprint does not launch. That is a pre-launch gate in the app, not advice in a manual.
Open, and quiet. AGPL-3.0, desktop app and sync server both in the repository, and no analytics SDK anywhere in the source. macOS, Windows, Linux.