[Ubuntu-x-swat] [Bug 1731102] [NEW] Poor performance with Wayland
Public bug reported: When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE env var) I see the following issues on this hardware: * Jerky animations (glxgears stutters noticably) * Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is under load, appearing to worsen over time (> 8 hours uptime) * High CPU usage when mousing over icons in left-hand side Unity dock (20-30%), also causing mouse cursor to stutter * 15fps in Kodi and poor video playback framerate * 30-40% CPU usage in Kodi when program idle * Gnome shell frequently using 25% of CPU or more All issues disappear when using x11 mode (again confirmed with XDG_SESSION_TYPE env var). Performance in that case seems as good as 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 BootLog: * Setting up X socket directories... [240G [234G[ OK ] * Restoring resolver state... [240G [234G[ OK ] Starting jabber server: ejabberd CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 13:03:08 2017 DistUpgraded: 2017-11-07 09:38:15,448 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6310] [19da:a191] InstallationDate: Installed on 2011-12-05 (2165 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=e1bf9820-e70e-4e84-9037-621437cc90f1 ro radeon.audio=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-11-06 (2 days ago) dmi.bios.date: 10/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/28/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 18 20:39:16 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputRiitek Micro Keyboard KEYBOARD, id 8 inputRiitek Micro Keyboard MOUSE, id 9 inputRiitek Micro Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful performance ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1731102 Title: Poor performance with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1731102/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1068661] Re: 1002:6740 Unity does not load after installing fglrx-installer Radeon HD 6700M Series
Hello, I have a 7770 and encountered this problem. I fixed it by uninstalling fglrx and installing fglrx-updates. My motherboard has no integrated graphics. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1068661 Title: 1002:6740 Unity does not load after installing fglrx-installer Radeon HD 6700M Series To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1068661/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 756237] Re: wxRuby crashes with segmentation fault in pixman_image_composite32
This bug seems to be also occurring for GNUstep in Debian and Ubuntu. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613221 ** Bug watch added: Debian Bug tracker #613221 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613221 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to pixman in Ubuntu. https://bugs.launchpad.net/bugs/756237 Title: wxRuby crashes with segmentation fault in pixman_image_composite32 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 756237] Re: wxRuby crashes with segmentation fault in pixman_image_composite32
I re-tested this in Natty and it still happened. But going off the suggestion in that bug, I recompiled wxruby while excluding GLCanvas, and I found the problem doesn't occur, wxruby works fine. Maybe the issue is in Mesa as the bug suggests. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to pixman in Ubuntu. https://bugs.launchpad.net/bugs/756237 Title: wxRuby crashes with segmentation fault in pixman_image_composite32 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 756237] Re: wxRuby crashes with segmentation fault in pixman_image_composite32
** Description changed:
+ Edited: I corrected the repro steps, thanks Marvin
+
This is a strange one, I'm not sure exactly where the fault lies.
Basically, performing almost any operation in a wxRuby app causes a
crash in pixman_image_composite32. This crash doesn't occur when running
regular wxWidgets apps or wxPython apps. The problem occurs on both ruby
1.8 and 1.9.1. It also occurs across all versions of wxRuby. The bug
doesn't show up on all linux distos (success has been reported with Arch
linux) but I think that's determined by the version of pixman that the
distro is using.
To repro:
1. Install ruby 1.9.1: sudo apt-get install ruby1.9.1
- 2. Install the wxWidgets gem: sudo gem1.9.1 install wxruby
- 3. Run the wxRuby bigdemo sample: ruby1.9.1
/var/lib/gems/1.9.1/gems/wxruby-2.0.0-x86_64-linux/samples/bigdemo/bigdemo.rb
+ 2. Install the wxWidgets gem: sudo gem1.9.1 install wxruby-ruby19
+ 3. Run the wxRuby bigdemo sample: ruby1.9.1
/var/lib/gems/1.9.1/gems/wxruby-ruby19-2.0.0-x86_64-linux/samples/bigdemo/bigdemo.rb
4. A segmentation fault occurs.
-
I've got wxRuby working by disabling some code in pixman. In the file
pixman/pixman.c, function lookup_composite_function, I
ifdef-ed out the following code:
- for (i = 0; i N_CACHED_FAST_PATHS; ++i)
- {
- const pixman_fast_path_t *info = (cache-cache[i].fast_path);
+ for (i = 0; i N_CACHED_FAST_PATHS; ++i)
+ {
+ const pixman_fast_path_t *info = (cache-cache[i].fast_path);
- /* Note that we check for equality here, not whether
- * the cached fast path matches. This is to prevent
- * us from selecting an overly general fast path
- * when a more specific one would work.
- */
- if (info-op == op
- info-src_format == src_format
- info-mask_format == mask_format
- info-dest_format == dest_format
- info-src_flags == src_flags
- info-mask_flags == mask_flags
- info-dest_flags == dest_flags
- info-func)
- {
- *out_imp = cache-cache[i].imp;
- *out_func = cache-cache[i].fast_path.func;
+ /* Note that we check for equality here, not whether
+ * the cached fast path matches. This is to prevent
+ * us from selecting an overly general fast path
+ * when a more specific one would work.
+ */
+ if (info-op == op
+ info-src_format == src_format
+ info-mask_format == mask_format
+ info-dest_format == dest_format
+ info-src_flags == src_flags
+ info-mask_flags == mask_flags
+ info-dest_flags == dest_flags
+ info-func)
+ {
+ *out_imp = cache-cache[i].imp;
+ *out_func = cache-cache[i].fast_path.func;
- goto update_cache;
- }
+ goto update_cache;
+ }
}
The bug doesn't occur after this modified version of pixman has been
installed. As far as I can see, the cache-cache[i].fast_path.func
pointer is pointing to an invalid location. I think the usual target of
these pointers is the following variable in pixman.c:
PIXMAN_DEFINE_THREAD_LOCAL (cache_t, fast_path_cache);
This thread local variable seems to be uninitialized or filled with
garbage when the crash occurs.
-
Here's a backtrace from ruby 1.9.1 illustrating the crash:
-- C level backtrace information ---
/usr/lib/libruby-1.9.1.so.1.9(rb_vm_bugreport+0x5f) [0x7fdd5531be8f]
/usr/lib/libruby-1.9.1.so.1.9(+0x58a56) [0x7fdd55226a56]
/usr/lib/libruby-1.9.1.so.1.9(rb_bug+0xb3) [0x7fdd55226bc3]
/usr/lib/libruby-1.9.1.so.1.9(+0xedde5) [0x7fdd552bbde5]
/lib/libpthread.so.0(+0xfb40) [0x7fdd54fc0b40]
/usr/local/lib/libpixman-1.so.0(pixman_image_composite32+0x300)
[0x7fdd4a296700]
/usr/lib/libcairo.so.2(+0x29463) [0x7fdd4b3b9463]
/usr/lib/libcairo.so.2(+0x2a61c) [0x7fdd4b3ba61c]
/usr/lib/libcairo.so.2(+0x2c31d) [0x7fdd4b3bc31d]
/usr/lib/libcairo.so.2(+0x2c55e) [0x7fdd4b3bc55e]
/usr/lib/libcairo.so.2(+0x49f56) [0x7fdd4b3d9f56]
/usr/lib/libcairo.so.2(+0x2243e) [0x7fdd4b3b243e]
/usr/lib/libcairo.so.2(cairo_fill_preserve+0x1d) [0x7fdd4b3a943d]
/usr/lib/libcairo.so.2(cairo_fill+0x9) [0x7fdd4b3a9469]
/usr/lib/librsvg-2.so.2(+0x2a1b0) [0x7fdd43bc91b0]
/usr/lib/librsvg-2.so.2(+0x248a0) [0x7fdd43bc38a0]
/usr/lib/librsvg-2.so.2(+0x1eb53) [0x7fdd43bbdb53]
/usr/lib/librsvg-2.so.2(+0x1f093) [0x7fdd43bbe093]
/usr/lib/librsvg-2.so.2(+0x1eb53) [0x7fdd43bbdb53]
/usr/lib/librsvg-2.so.2(+0x1f093) [0x7fdd43bbe093]
/usr/lib/librsvg-2.so.2(+0x1eb53) [0x7fdd43bbdb53]
/usr/lib/librsvg-2.so.2(+0x1ef64) [0x7fdd43bbdf64]
/usr/lib/librsvg-2.so.2(+0x1eb53) [0x7fdd43bbdb53]
/usr/lib/librsvg-2.so.2(rsvg_handle_render_cairo_sub+0xca) [0x7fdd43bc9b1a]
/usr/lib/librsvg-2.so.2(rsvg_handle_get_pixbuf_sub+0x105) [0x7fdd43bca065]
[Ubuntu-x-swat] [Bug 756237] [NEW] wxRuby crashes with segmentation fault in pixman_image_composite32
Public bug reported:
This is a strange one, I'm not sure exactly where the fault lies.
Basically, performing almost any operation in a wxRuby app causes a
crash in pixman_image_composite32. This crash doesn't occur when running
regular wxWidgets apps or wxPython apps. The problem occurs on both ruby
1.8 and 1.9.1. It also occurs across all versions of wxRuby. The bug
doesn't show up on all linux distos (success has been reported with Arch
linux) but I think that's determined by the version of pixman that the
distro is using.
To repro:
1. Install ruby 1.9.1: sudo apt-get install ruby1.9.1
2. Install the wxWidgets gem: sudo gem1.9.1 install wxruby
3. Run the wxRuby bigdemo sample: ruby1.9.1
/var/lib/gems/1.9.1/gems/wxruby-2.0.0-x86_64-linux/samples/bigdemo/bigdemo.rb
4. A segmentation fault occurs.
I've got wxRuby working by disabling some code in pixman. In the file
pixman/pixman.c, function lookup_composite_function, I
ifdef-ed out the following code:
for (i = 0; i N_CACHED_FAST_PATHS; ++i)
{
const pixman_fast_path_t *info = (cache-cache[i].fast_path);
/* Note that we check for equality here, not whether
* the cached fast path matches. This is to prevent
* us from selecting an overly general fast path
* when a more specific one would work.
*/
if (info-op == op
info-src_format == src_format
info-mask_format == mask_format
info-dest_format == dest_format
info-src_flags == src_flags
info-mask_flags == mask_flags
info-dest_flags == dest_flags
info-func)
{
*out_imp = cache-cache[i].imp;
*out_func = cache-cache[i].fast_path.func;
goto update_cache;
}
}
The bug doesn't occur after this modified version of pixman has been
installed. As far as I can see, the cache-cache[i].fast_path.func
pointer is pointing to an invalid location. I think the usual target of
these pointers is the following variable in pixman.c:
PIXMAN_DEFINE_THREAD_LOCAL (cache_t, fast_path_cache);
This thread local variable seems to be uninitialized or filled with
garbage when the crash occurs.
Here's a backtrace from ruby 1.9.1 illustrating the crash:
-- C level backtrace information ---
/usr/lib/libruby-1.9.1.so.1.9(rb_vm_bugreport+0x5f) [0x7fdd5531be8f]
/usr/lib/libruby-1.9.1.so.1.9(+0x58a56) [0x7fdd55226a56]
/usr/lib/libruby-1.9.1.so.1.9(rb_bug+0xb3) [0x7fdd55226bc3]
/usr/lib/libruby-1.9.1.so.1.9(+0xedde5) [0x7fdd552bbde5]
/lib/libpthread.so.0(+0xfb40) [0x7fdd54fc0b40]
/usr/local/lib/libpixman-1.so.0(pixman_image_composite32+0x300) [0x7fdd4a296700]
/usr/lib/libcairo.so.2(+0x29463) [0x7fdd4b3b9463]
/usr/lib/libcairo.so.2(+0x2a61c) [0x7fdd4b3ba61c]
/usr/lib/libcairo.so.2(+0x2c31d) [0x7fdd4b3bc31d]
/usr/lib/libcairo.so.2(+0x2c55e) [0x7fdd4b3bc55e]
/usr/lib/libcairo.so.2(+0x49f56) [0x7fdd4b3d9f56]
/usr/lib/libcairo.so.2(+0x2243e) [0x7fdd4b3b243e]
/usr/lib/libcairo.so.2(cairo_fill_preserve+0x1d) [0x7fdd4b3a943d]
/usr/lib/libcairo.so.2(cairo_fill+0x9) [0x7fdd4b3a9469]
/usr/lib/librsvg-2.so.2(+0x2a1b0) [0x7fdd43bc91b0]
/usr/lib/librsvg-2.so.2(+0x248a0) [0x7fdd43bc38a0]
/usr/lib/librsvg-2.so.2(+0x1eb53) [0x7fdd43bbdb53]
/usr/lib/librsvg-2.so.2(+0x1f093) [0x7fdd43bbe093]
/usr/lib/librsvg-2.so.2(+0x1eb53) [0x7fdd43bbdb53]
/usr/lib/librsvg-2.so.2(+0x1f093) [0x7fdd43bbe093]
/usr/lib/librsvg-2.so.2(+0x1eb53) [0x7fdd43bbdb53]
/usr/lib/librsvg-2.so.2(+0x1ef64) [0x7fdd43bbdf64]
/usr/lib/librsvg-2.so.2(+0x1eb53) [0x7fdd43bbdb53]
/usr/lib/librsvg-2.so.2(rsvg_handle_render_cairo_sub+0xca) [0x7fdd43bc9b1a]
/usr/lib/librsvg-2.so.2(rsvg_handle_get_pixbuf_sub+0x105) [0x7fdd43bca065]
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so(+0xd6b)
[0x7fdd43dfdd6b]
/usr/lib/libgdk_pixbuf-2.0.so.0(gdk_pixbuf_loader_close+0xf9) [0x7fdd4ffce889]
/usr/lib/libgdk_pixbuf-2.0.so.0(+0x89a6) [0x7fdd4ffcc9a6]
/usr/lib/libgdk_pixbuf-2.0.so.0(gdk_pixbuf_new_from_stream_at_scale+0x81)
[0x7fdd4ffccb01]
/usr/lib/libgtk-x11-2.0.so.0(+0x104eec) [0x7fdd507b3eec]
/usr/lib/libgtk-x11-2.0.so.0(gtk_icon_info_load_icon+0x72) [0x7fdd507b4612]
/usr/lib/libgtk-x11-2.0.so.0(gtk_icon_theme_load_icon+0x13f) [0x7fdd507b685f]
/usr/lib/libgtk-x11-2.0.so.0(gtk_icon_set_render_icon+0x5ea) [0x7fdd507b0faa]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_render_icon+0xea) [0x7fdd5090834a]
/usr/lib/libgtk-x11-2.0.so.0(+0x1185d4) [0x7fdd507c75d4]
/usr/lib/libgtk-x11-2.0.so.0(+0x1185f9) [0x7fdd507c75f9]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xa9) [0x7fdd4f7299b9]
/usr/lib/libgobject-2.0.so.0(+0x246b1) [0x7fdd4f73f6b1]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7e6) [0x7fdd4f7412a6]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_by_name+0x208) [0x7fdd4f7415f8]
/usr/lib/libgtk-x11-2.0.so.0(+0x1a5138) [0x7fdd50854138]
/usr/lib/libgtk-x11-2.0.so.0(+0x85967) [0x7fdd50734967]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xa9) [0x7fdd4f7299b9]
/usr/lib/libgobject-2.0.so.0(+0x246b1)
