5 Commits
Author SHA1 Message Date
7e49123464 Bound the host GPU probe and fail loudly (#985)
* Bound the host GPU probe and fail loudly

A display that accepts connections but never answers the X handshake
left Firefox inside getContext() forever, and the launch with it. Both
launchers now give the probe's launch, page read and cleanup one
30-second deadline, and a timeout raises with the executable and
DISPLAY it was probing instead of hanging.

The Python reader runs in a daemon thread, so a browser call that
cannot be cancelled does not keep the interpreter alive after the
timeout. The TypeScript probe closes its browser on the same failure
path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Probe the host GPU in a child process so a timeout stops the browser

A thread cannot be stopped, so a probe that timed out kept its browser and
Playwright driver running until the interpreter exited, and each later launch
retried the probe and started another. The probe now runs in a child
interpreter; terminating it on a timeout closes its pipe to the driver, which
shuts the browser down. A child also starts from inside AsyncCamoufox's
running asyncio loop, which the sync API refuses.

The tests run the real probe: a stand-in browser that never answers must be
gone after the timeout, and a missing executable reports Playwright's error.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Jake Writer <jake_writer@jobharvest.com>
2026-11-10 18:41:56 +00:00
Jake WriterandClaude Opus 5.5 601918959f Report the software renderer on a host that renders in software (#1006)
A host with no working GPU driver kept a drawn GPU name, on the theory that it
read as a machine whose driver failed to load. It does not. Firefox reads
UNMASKED_RENDERER_WEBGL and the pixels from one GL context, so stock 159 on an
RX 7900 XTX with a broken Mesa driver reports llvmpipe with the same readPixels
hash as Xvfb. A GPU name over those pixels never happens on a real machine, and
two reads expose it.

The launchers now claim the host's software renderer as they claim its GPU, so
name and pixels agree without canvas noise. A drawn identity still never picks
a software renderer, and a software renderer fpgen has not recorded on that OS
takes the same path as an unrecorded GPU.

This reads as a server or a broken driver, and checks that flag llvmpipe will
flag it. Rendering on a GPU with headless="virtual-gpu" is the way to report one.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 00:58:08 +00:00
Jake Writer f30f6e8368 Merge pull request #912 from JWriter20/feat/virtual-gpu-display
Add headless="virtual-gpu": render on a named GPU with no monitor attached
2026-10-19 01:51:33 +00:00
Jake WriterandClaude Opus 5.5 5c1fd578ad Read a build's version from its own bundle, refuse browser= with a binary, and cover the canvas whenever the GPU is not the host's
- A named executable's application.ini is found beside it, or in
  Contents/Resources of a macOS app bundle (pkgman.build_file / buildFile),
  and a named executable without one raises instead of borrowing the paired
  build's version. browser= on macOS no longer raises CamoufoxNotInstalled
  or claims the wrong Firefox major.
- browser= together with executable_path or CAMOUFOX_EXECUTABLE_PATH raises
  ValueError instead of silently dropping browser=.
- One function per launcher (plan_rendering / planRendering) decides whether
  the identity claims the host's GPU or the canvas is covered, for the launch
  and for the host identity its contexts keep. A GPU named by webgl_config or
  a preset, or a host GPU fpgen never recorded, now covers the canvas by
  default, and such a browser binds no context to the host.
- setWebgpu keeps a caller pref set to null, as Python's setdefault does.
- stock-gpu-parity verifies SHA256SUMS.asc against Mozilla's release key and
  uses camoufox.webgl.recorded_devices instead of private helpers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-09 13:38:46 -06:00
Jake WriterandClaude Opus 5.5 159aebedac Claim the host's GPU on its own OS, cover canvas and WebGPU on another, and follow Firefox 156 for browser-owned GPU values
Canvas, WebGL and WebGPU output come from the real OS, driver and GPU. On the
host's OS the identity now claims the GPU Firefox actually renders with; on
another OS canvas and WebGL readback use privacy.resistFingerprinting's canvas
placeholder (canvas_noise, on by default only for another OS, with a LeakWarning).

WebGPU follows the claimed device: navigator.gpu only where Firefox exposes it
(Windows, Apple Silicon), and the host's adapter only when the identity claims
the host's hardware GPU. Otherwise gfx.blacklist.webgpu marks the device
blocked, so requestAdapter() resolves to null as it does for real users on a
blocked or software GPU. The pref is read at startup, so it goes through
CAMOU_PREFS.

Spoofed avail-screen and touch values now pass through stock baseline
fingerprinting protection for the claimed platform (screen-spoofing,
touchscreen-fingerprint-spoofing).

fpgen's records are mostly Firefox 146, and two WebGL values are decided by
the browser rather than the device: Windows extension lists now include
EXT_depth_clamp (ANGLE's D3D11 backend reports it on every feature level in
156), and WebGL1's ALIASED_LINE_WIDTH_RANGE takes the device's WebGL2 value
(Firefox 156 no longer forces a compatibility profile for WebGL1 on Linux).

A new parity guard, stock-gpu-parity, compares stock Firefox at the build's
version, stock Firefox at the release fpgen recorded, and Camoufox claiming the
host's GPU, and fails when Camoufox differs from stock on a value the two stock
releases disagree on. Decisions are recorded in ci/tribal-rules.yml
(cross-os-canvas-is-the-rfp-placeholder, webgpu-follows-the-claimed-device,
webgl-browser-owned-values-follow-firefox).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 19:08:30 -06:00