Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Apr 2021 09:58:27 +0000
From:      bugzilla-noreply@freebsd.org
To:        gecko@FreeBSD.org
Subject:   [Bug 255344] www/firefox: enable HW_COMPOSITING by default
Message-ID:  <bug-255344-21738@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255344

            Bug ID: 255344
           Summary: www/firefox: enable HW_COMPOSITING by default
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: gecko@FreeBSD.org
          Reporter: skrechy@gmail.com
          Assignee: gecko@FreeBSD.org
             Flags: maintainer-feedback?(gecko@FreeBSD.org)

Hello,

I've recently updated my PC and added a dGPU nVidia GT710. Up until now I w=
as
using the built-in graphics in my AMD processor. I don't remember having any
issues. However, after switching to nVidia and downloaded nvidia-drivers
package I started noticing tearing/skipping artifacts when scrolling in
Firefox. Since I'm new to nvidia tools and configurations, I've spent sever=
al
days trying to find what is causing the tearing problem while mainly suspec=
ting
the driver or KDE. At some point I've noticed that this tearing problem is
happening only in Firefox, and resizing/moving windows around the screen was
smooth. So, apparently the problem was neither in the driver nor KDE, but in
Firefox. I've checked what is written in about:support and noticed the
following:

HW_COMPOSITING: available by default, blocked by env: Acceleration blocked =
by
platform

After forcing the hw compositing with `layers.acceleration.force-enabled=3D=
True`
in about:config scrolling became silky smooth.=20

So, is there a reason for disabling hardware compositing by default? In my
opinion, with the state of nvidia and amd drivers currently, most of the us=
ers
would expect these relatively basic accelerations to be enabled by default.=
 If
they have problems with something, just then should they try to disable the
problematic feature. If there are serious problems, then at least a
post-installation message pointing the user to enable acceleration will be =
very
beneficial in both performance and tearing-free experience.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255344-21738>