Latest Firefox update fixes rare graphics bug with Nvidia GPUs, just one day after it was reported

Table of Contents
It’s not as popular these days, but there are still plenty of us using it. Firefox has had to implement a quick patch to its browser to address some corruption from its latest big update. 139.0.1 was released just yesterday, and two days after the main patch targeting Nvidia graphics cards specifically, which had issues with the live version.
The patch comes thanks to it being posted on Bugzilla (bug 1968876) the previous day, as the reporter, Jan Dvorak, encountered this issue on their computer. It is rather specific, featuring an RTX 3080 with two monitors connected via DisplayPort with varying refresh rates and resolutions.
Having a 1440p 144Hz primary display and 1080p 60Hz was not playing nicely with Firefox 139.0. After opening a site on the first monitor and playing YouTube in another window on monitor two at 60 FPS, it caused corruption inside the window on monitor one by flashing parts of the video when hovering over any graphical elements in it.
A brief video of the artifacting
A rather frustrating artifacting error to get, so if you are experiencing it on the browser, be sure to update it to remove the problem.
Firefox 139.0 update
Mozilla’s 139.0 Firefox update adds a few new features to enjoy in the browser. Some of the highlights include:
- Full-page translations are available within Firefox extension pages.
- New Tab custom wallpaper and colors option is now available, along with the ability for custom image uploads.
- Link previews are available in Firefox Labs in settings. After enabling, you can press Alt+Shift when hovering over links to see the preview.
- PNG images with transparency keep their transparency when pasted now.
- Security fixes.
Even with Firefox only garnering 2.55% of the market share (according to StatCounter), it’s great to see it up to date with these bug fixes and improvements as one of those users. The 139.0 patch notes make note of the unusual multi-monitor bug, which was, of course, fixed in the following 139.1 update.