<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 - link_shader and deserialize_glsl_program suddenly consume huge amount of RAM"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111077">111077</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>link_shader and deserialize_glsl_program suddenly consume huge amount of RAM
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>18.3
</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>blocker
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/Gallium/radeonsi
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>roland@rptd.ch
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=144715" name="attach_144715" title="Valgrind massif log">attachment 144715</a> <a href="attachment.cgi?id=144715&action=edit" title="Valgrind massif log">[details]</a></span>
Valgrind massif log
Since a recent update a few days ago an application which barely consumes 2G
RAM at full load is very slow to load and compiling shaders causes over 16G RAM
to be consumed when the app eventually crashes.
I don't know what exactly in the update caused problems but certainly Mesa, the
amdgpu driver and LLVM did get updates.
I also tried using Mesa 19.x but the problem is the same.
Driver is xf86-video-amdgpu-19.0.1 . LLVM is 7.0.x .
I've already deleted the mesa shader cache and all caches the application
creates. I've totally recompiled the system (GenToo) to make sure no strange
problems can be around. I've also tried with a completely fresh user to run the
app.
Using valgrind --tool=massif the culprit seems to be ralloc_size which is
called by the two above mentioned methods. I've attached a massif log of a
couple of seconds running of the application and shutting it down before memory
skyrockets even more. The app in question shows at that point of time only an
empty scene with a simple shader doing a sky-box. The rest is Non OpenGL UI
stuff.
Classified this as blocker since as soon as you try loading more shaders not
even 32G seems to be enough to cope with the rampaging glsl compiler.</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>