<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 - Latest intel drivers from git cause massive use of shared memory on haswell system"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100632">100632</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Latest intel drivers from git cause massive use of shared memory on haswell system
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>sergio.callegari@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Seen on KUbuntu 16.10 (yakkety) with an haswell laptop.
Using the stock intel drivers shipped with the distro, everything is fine.
Using the "oibaf ppa", which is a way of getting the latest video drivers
including latest git tip for mesa, libdrm, libva, xorg-video-intel you get
opengl 4 and a much more modern stack.
However, since a few days ago (hard to say exactly when, would guess about the
first days of april), a nasty phenomenon started to show up, consisting in more
and more memory being used by the system, until the system starts swapping and
freezes.
Using the free command, the item that starts growing uncontrollably is the
"shared" entry. I have seen it going above 7GB.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>