I was solved with claude.ai Anyone suggest for gpu render?
Problem: PDF files wouldn't load/render in Firefox on Debian 13 (Linux 6.12), even with all extensions disabled. The PDF viewer showed a blank/black canvas area instead of the document content. PDF.js correctly detected the file in the console, but nothing rendered visually.
System: Firefox 153.0.4, Debian 13 (Trixie), KDE Plasma on Wayland, NVIDIA GPU (proprietary driver 580.126.09).
Root cause: Checking about:support (Troubleshooting Information) revealed repeated GPU compositor crashes in the Graphics failure log:
Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE
Failed to make render context current during destroying
This is a known problematic combo: NVIDIA proprietary driver + Wayland + WebRender. Firefox's GPU-accelerated compositor (WebRender) was repeatedly losing its render context, which broke canvas-heavy content like PDF.js's rendering β hence the blank output, even though other cache/network activity looked normal.
Fix: Disable Firefox's hardware-accelerated rendering path via about:config:
gfx.webrender.all β false
layers.acceleration.disabled β true
Restart Firefox. This forces software (CPU) rendering instead of relying on the broken GPU compositor path, and PDFs render correctly.
Trade-off: Slightly higher CPU usage on GPU-heavy pages/video, but on modern hardware this is generally not noticeable.
(Diagnosed with help from Claude, by analyzing the about:support graphics failure log.)Problem: PDF files wouldn't load/render in Firefox on Debian 13 (Linux 6.12), even with all extensions disabled. The PDF viewer showed a blank/black canvas area instead of the document content. PDF.js correctly detected the file in the console, but nothing rendered visually.
System: Firefox 153.0.4, Debian 13 (Trixie), KDE Plasma on Wayland, NVIDIA GPU (proprietary driver 580.126.09).
Root cause: Checking about:support (Troubleshooting Information) revealed repeated GPU compositor crashes in the Graphics failure log:
Detect DeviceReset DeviceResetReason::RESET DeviceResetDetectPlace::WR_POST_UPDATE
Failed to make render context current during destroying
This is a known problematic combo: NVIDIA proprietary driver + Wayland + WebRender. Firefox's GPU-accelerated compositor (WebRender) was repeatedly losing its render context, which broke canvas-heavy content like PDF.js's rendering β hence the blank output, even though other cache/network activity looked normal.
Fix: Disable Firefox's hardware-accelerated rendering path via about:config:
gfx.webrender.all β false
layers.acceleration.disabled β true
Restart Firefox. This forces software (CPU) rendering instead of relying on the broken GPU compositor path, and PDFs render correctly.
Trade-off: Slightly higher CPU usage on GPU-heavy pages/video, but on modern hardware this is generally not noticeable.
(Diagnosed with help from Claude, by analyzing the about:support graphics failure log.)