Bug 263645 – [GTK] The rendering of the fonts look blurred (NVIDIA card), if I launch the application with WEBKIT_DISABLE_COMPOSITING_MODE=1 they look perfect

• Component: WebKitGTK
• Status: NEW

[Óscar]

Created attachment 468328 [details]
cinny_bad.png, blurring of fonts visible. cinny_ok.png app launched with WEBKIT_DISABLE_COMPOSITING_COMPOSITING_MODE=1

First of all my apologies if this bug is duplicated, I have been searching but have not found anything similar except for #261874 but it describes a different behaviour. Possibly both bugs are related.

Fonts are rendered blurred with WebKitGTK unless the application is launched with WEBKIT_DISABLE_COMPOSITING_COMPOSITING_MODE=1. It is highly possible that this only happens with NVIDIA cards and proprietary drivers with X11.

Card: NVIDIA GeForce RTX 2060 SUPER
WebKitGTK version: 2.42.1
Environment: GNOME 45.0 (X11)

[Adrian Perez]

Created attachment 468329 [details]
Good rendering, with WEBKIT_DISABLE_COMPOSITING_COMPOSITING_MODE=1

(File extracted from tarball, for convenience.)

[Adrian Perez]

Created attachment 468330 [details]
Bad rendering

(File extracted from tarball, for convenience.)

[Óscar]

The situation with recent versions has worsened. Now it simply displays nothing and gives the following error repeated several times.

AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer

With WEBKIT_DISABLE_COMPOSITING_COMPOSITING_MODE=1 it still works well.

[Thomas Zajic]

Hi,

I never had the problem with blurred fonts, but I'm also still (at least since 2.42) experiencing the "emtpy renderings" in GTK 3 applications. While as of bug #261874 I also had the same problem with GTK 4 applications, the GTK 4 problem seems to have been fixed meanwhile. Apps like "epiphany" work fine now. Just for the record, I'm currently using gtk-4.16.3.

GTK 3 apps, however, still need either WEBKIT_DISABLE_DMABUF_RENDERER=1 or WEBKIT_DISABLE_COMPOSITING_MODE=1 to work properly. Without any of these two set to 1, apps like "yelp" or "liferea" will only display an either empty or black area where WebKitGTK's output should show up. On the console, the error message "AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer" is repeated several times.

My setup:

* Slackware64-15.0
* GNOME-47.0, running a ...
* gnome-flashback-3.54.0 session using ...
* metacity-3.54.0 in an *uncomposited* X11 environment ("gsettings get org.gnome.metacity compositor" => 'none')
* gtk+-3.24.43
* webkitgtk-2.46.1
* GPU: NVIDIA GeForce GTX 1660 Ti
* GPU driver: NVIDIA-Linux-x86_64-550.120 (ie. the binary, proprietary one)
* GPU driver settings:
/sys/module/nvidia_drm/parameters/fbdev:Y
/sys/module/nvidia_drm/parameters/modeset:Y
/sys/module/nvidia_modeset/parameters/config_file:(null)
/sys/module/nvidia_modeset/parameters/disable_hdmi_frl:N
/sys/module/nvidia_modeset/parameters/disable_vrr_memclk_switch:N
/sys/module/nvidia_modeset/parameters/fail_malloc:-1
/sys/module/nvidia_modeset/parameters/hdmi_deepcolor:N
/sys/module/nvidia_modeset/parameters/malloc_verbose:N
/sys/module/nvidia_modeset/parameters/opportunistic_display_sync:Y
/sys/module/nvidia_modeset/parameters/output_rounding_fix:Y
/sys/module/nvidia_modeset/parameters/vblank_sem_control:N
/sys/module/nvidia_uvm/parameters/uvm_ats_mode:1
/sys/module/nvidia_uvm/parameters/uvm_block_cpu_to_cpu_copy_with_ce:0
/sys/module/nvidia_uvm/parameters/uvm_channel_gpfifo_loc:auto
/sys/module/nvidia_uvm/parameters/uvm_channel_gpput_loc:auto
/sys/module/nvidia_uvm/parameters/uvm_channel_num_gpfifo_entries:1024
/sys/module/nvidia_uvm/parameters/uvm_channel_pushbuffer_loc:auto
/sys/module/nvidia_uvm/parameters/uvm_conf_computing_channel_iv_rotation_limit:2147483648
/sys/module/nvidia_uvm/parameters/uvm_cpu_chunk_allocation_sizes:2166784
/sys/module/nvidia_uvm/parameters/uvm_debug_enable_push_acquire_info:0
/sys/module/nvidia_uvm/parameters/uvm_debug_enable_push_desc:0
/sys/module/nvidia_uvm/parameters/uvm_debug_prints:0
/sys/module/nvidia_uvm/parameters/uvm_disable_hmm:N
/sys/module/nvidia_uvm/parameters/uvm_downgrade_force_membar_sys:1
/sys/module/nvidia_uvm/parameters/uvm_enable_builtin_tests:0
/sys/module/nvidia_uvm/parameters/uvm_enable_debug_procfs:0
/sys/module/nvidia_uvm/parameters/uvm_enable_va_space_mm:1
/sys/module/nvidia_uvm/parameters/uvm_exp_gpu_cache_peermem:0
/sys/module/nvidia_uvm/parameters/uvm_exp_gpu_cache_sysmem:0
/sys/module/nvidia_uvm/parameters/uvm_fault_force_sysmem:0
/sys/module/nvidia_uvm/parameters/uvm_force_prefetch_fault_support:0
/sys/module/nvidia_uvm/parameters/uvm_global_oversubscription:1
/sys/module/nvidia_uvm/parameters/uvm_leak_checker:0
/sys/module/nvidia_uvm/parameters/uvm_page_table_location:(null)
/sys/module/nvidia_uvm/parameters/uvm_peer_copy:phys
/sys/module/nvidia_uvm/parameters/uvm_perf_access_counter_batch_count:256
/sys/module/nvidia_uvm/parameters/uvm_perf_access_counter_mimc_migration_enable:-1
/sys/module/nvidia_uvm/parameters/uvm_perf_access_counter_momc_migration_enable:-1
/sys/module/nvidia_uvm/parameters/uvm_perf_access_counter_threshold:256
/sys/module/nvidia_uvm/parameters/uvm_perf_fault_batch_count:256
/sys/module/nvidia_uvm/parameters/uvm_perf_fault_coalesce:1
/sys/module/nvidia_uvm/parameters/uvm_perf_fault_max_batches_per_service:20
/sys/module/nvidia_uvm/parameters/uvm_perf_fault_max_throttle_per_service:5
/sys/module/nvidia_uvm/parameters/uvm_perf_fault_replay_policy:2
/sys/module/nvidia_uvm/parameters/uvm_perf_fault_replay_update_put_ratio:50
/sys/module/nvidia_uvm/parameters/uvm_perf_map_remote_on_eviction:1
/sys/module/nvidia_uvm/parameters/uvm_perf_map_remote_on_native_atomics_fault:0
/sys/module/nvidia_uvm/parameters/uvm_perf_migrate_cpu_preunmap_block_order:2
/sys/module/nvidia_uvm/parameters/uvm_perf_migrate_cpu_preunmap_enable:1
/sys/module/nvidia_uvm/parameters/uvm_perf_pma_batch_nonpinned_order:6
/sys/module/nvidia_uvm/parameters/uvm_perf_prefetch_enable:1
/sys/module/nvidia_uvm/parameters/uvm_perf_prefetch_min_faults:1
/sys/module/nvidia_uvm/parameters/uvm_perf_prefetch_threshold:51
/sys/module/nvidia_uvm/parameters/uvm_perf_reenable_prefetch_faults_lapse_msec:1000
/sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_enable:1
/sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_epoch:2000
/sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_lapse_usec:500
/sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_max_resets:4
/sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_nap:1
/sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_pin:300
/sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_pin_threshold:10
/sys/module/nvidia_uvm/parameters/uvm_perf_thrashing_threshold:3
/sys/module/nvidia_uvm/parameters/uvm_release_asserts:1
/sys/module/nvidia_uvm/parameters/uvm_release_asserts_dump_stack:0
/sys/module/nvidia_uvm/parameters/uvm_release_asserts_set_global_error:0

If you need any more information, please let me know.

Thanks for listening! :-)
Thomas

[Michael Catanzaro]

(In reply to Thomas Zajic from comment #4)
> Hi,
> 
> I never had the problem with blurred fonts, but I'm also still (at least
> since 2.42) experiencing the "emtpy renderings" in GTK 3 applications.

Please report a new bug. You're not going to get much help in a bug report about blurry fonts if your problem isn't blurry fonts!

[Thomas Zajic]

Haha, yes, you've got a good point there of course! :-)

Judging from comment #3, though, I thought the OR's problem was not blurry fonts anymore, but that is has changed to exactly the problem that I am seeing. And when I searched Bugzilla for that specific error message ("AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer"), this was the only hit that popped up, so I thought it would make sense to add my 2 cents here. Plus I wanted to avoid cluttering the open bug list with a duplicate report ... O:-)

Maybe the OR (or somebody with enough Bugzilla admin power) could instead change the bug title to something matching the *actual* problem, so that it better describes the way it currently manifests?

But if you'd rather have a completely new bug report for this, then I can do that as well, no problem. ;-)

[Michael Catanzaro]

Please report a new bug for "AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer." Hopefully it will get more attention separately.

[Michael Catanzaro]

(In reply to Óscar from comment #3)
> The situation with recent versions has worsened. Now it simply displays
> nothing and gives the following error repeated several times.
> 
> AcceleratedSurfaceDMABuf was unable to construct a complete framebuffer
> 
> With WEBKIT_DISABLE_COMPOSITING_COMPOSITING_MODE=1 it still works well.

Are you still encountering this problem? Your comment in bug #278230 indicates you're no longer having trouble with NVIDIA graphics?

[Óscar]

(In reply to Michael Catanzaro from comment #8)
> Are you still encountering this problem? Your comment in bug #278230
> indicates you're no longer having trouble with NVIDIA graphics?

In bug  #278230 I meant that I have no crash type problems. This problem of blurred fonts fonts still occurs.

[Thomas Zajic]

(In reply to Michael Catanzaro from comment #7)
> Please report a new bug for "AcceleratedSurfaceDMABuf was unable to
> construct a complete framebuffer." Hopefully it will get more attention
> separately.

[x] done, see bug #281279 :-)

Thanks
Thomas