1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking Benchmarking Platform
Phoromatic Test Orchestration

Whoops, There's A Big Problem For Wayland GTK+

Wayland

Published on 18 March 2012 10:01 PM EDT
Written by Michael Larabel in Wayland
53 Comments

It turns out there's a rather serious issue for some systems when having Wayland support within GTK+ exposed, which may hinder the Wayland GTK+ availability in the near-term.

As I wrote about a few days ago, Wayland support isn't for end-users in Ubuntu 12.04 and the GTK+ version they are shipping is 3.4. GTK+ 3.4 has the Wayland GDK back-end that works as an alternative to the X11 back-end and can be dynamically utilized. With the supported GTK+ code, it's as easy as building it with the --enable-wayland-backend option, but that's not happening for Ubuntu 12.04 LTS or by any other major distribution right now as far as I'm aware. It turns out that for some users this is good to not have the Wayland support exposed.

Building the GTK+ Wayland support currently depends upon having cairo-gl, the OpenGL version of the Cairo drawing library. However, cairo-gl with the NVIDIA binary driver can be a memory-hungry mess. Using cairo-gl at this point with the NVIDIA binary driver appears to be a big mess. This isn't just about using additional memory when running GTK+ applications on Wayland (where the NVIDIA binary driver isn't even compatible at this point), but the GL version of Cairo on X11 would be shafted.

This memory usage problem only seems to be present for the NVIDIA binary driver, but the open-source NVIDIA (Nouveau) driver isn't affected, the AMD Catalyst driver, nor any of the other open-source drivers have a hard time dealing with cairo-gl.

The solution to this is either have NVIDIA address their driver issue(s) causing excessive memory usage with cairo-gl, ship multiple versions of Cairo on the system (but there's some packaging problems currently), or change how Cairo loads libGL such that it only happens when a client requests an OpenGL context. The alternative is just to let NVIDIA binary users burn through the additional system memory.

This issue is talked at length in this Wayland mailing list message.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux News
  1. NVIDIA's Proprietary Driver Is Moving Closer With Kernel Mode-Setting
  2. The Latest Linux Kernel Git Code Fixes The EXT4 RAID0 Corruption Problem
  3. Features Added To Mesa 10.6 For Open-Source GPU Drivers
  4. Ubuntu's LXD vs. KVM For The Linux Cloud
  5. Fedora Server 22 Benchmarks With XFS & The Linux 4.0 Kernel
  6. GCC 6 Gets Support For The IBM z13 Mainframe Server
  7. Fedora 22 Is Being Released Next Tuesday
  8. OpenWRT 15.05 Preparing Improved Security & Better Networking
  9. Using The New LLVM/Clang OpenMP Support
  10. Zapcc Claims To Be A "Much Faster C++ Compiler"
Latest Articles & Reviews
  1. Btrfs RAID 0/1 Benchmarks On The Linux 4.1 Kernel
  2. The State Of Various Firefox Features
  3. Intel Iris Graphics Performance With Mesa 10.6
  4. Fedora Workstation 22 Is Looking Great, Running Fantastic
Most Viewed News This Week
  1. The Linux 4.0 Kernel Currently Has An EXT4 Corruption Issue
  2. The Linux 4.0 EXT4 RAID Corruption Bug Has Been Uncovered
  3. AMDGPU Open-Source Driver Code Continues Maturing
  4. Oculus Rift Suspends Linux Development To Focus On Windows
  5. Microsoft Open-Sources The Windows Communication Foundation
  6. Another HTTPS Vulnerability Rattles The Internet
  7. LibreOffice 5.0 Open-Source Office Suite Has Been Branched
  8. Systemd 220 Has Finally Been Released