<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - XWayland [weston 1.6.0] takes all CPU and is very slow on eee-pc"
href="https://bugs.freedesktop.org/show_bug.cgi?id=86815">86815</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>XWayland [weston 1.6.0] takes all CPU and is very slow on eee-pc
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>XWayland
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>mildred-bug.freedesktop@mildred.fr
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>xorg-team@lists.x.org
</td>
</tr></table>
<p>
<div>
<pre>Running weston with the xwayland.so module on current ArchLinux (weston
1.6.0-1) cause on some computers XWayland to take all the CPU available (100%
of one CPU core out of the two cores available on the system), and is very
slow. X11 windows are shown but unusable.
This happens on a eee-pc 1005PE. Processor is dual core intel atom N450 with
integrated intel graphics. On another computer running the same distro (and
same package versions) but with an i7 processor, I have no problems, and
XWayland CPU usage is more than correct.
I noticed the following pattern:
- running an X11 application cause XWayland to consume the most CPU
- after some time focusing on a wayland native application, XWayland stops
eating CPU
- if focusing on the X11 window again (or simply hovering the mouse), CPU
consumption rise again to 100%
- wayland surfaces continue to be responsive (that's nice actually)
- I notice glitches on X11 window decorations (the title bar disappear, then
reappear). That may be unrelated though.
Looking at the Xwayland process using strace, I found a unusual number of
SIGALRM signals being catched by Xwayland. I have the following sequence
repeated many many many times:
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---
rt_sigreturn() = (number that varies a lot, 0, 1 and higher integers)
There are some ioctl in the mix and very few other system calls</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>