<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 - High memory usage in Black Mesa"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108946">108946</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>High memory usage in Black Mesa
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>18.2
</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>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Mesa core
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>marco.gerzb@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=142728" name="attach_142728" title="glxinfo">attachment 142728</a> <a href="attachment.cgi?id=142728&action=edit" title="glxinfo">[details]</a></span>
glxinfo
Hello,
Since some time this game keeps getting an out of memory error that makes it
crash (it's a 32bit binary). While reporting the issues to the game devs this
is the reason they gave to the users
(<a href="https://steamcommunity.com/app/362890/discussions/1/3307213006836757658/?ctp=7">https://steamcommunity.com/app/362890/discussions/1/3307213006836757658/?ctp=7</a>):
"... From what I noticed, more shaders game had - faster out of memory
occurred. Black Mesa has full (or almost full) support of SM 3.0 on Linux which
allowed us to use same shaders with same code on both platfroms, while opening
new horizons for our new dynamic lighting implementation. After first discovery
of issues with Mesa driver, to avoid out of memory I had to cut some of shader
combinations completely specifically for OpenGL version by introducing shader
platform flags that decide if particular part with some visual feature the of
shader will be compiled. That helped quite a lot, we were able to run Black
Mesa for a while on AMD with lowest settings and CSM being turned off. But
while Mesa is sharing same memory location in application's address space, it's
pretty hard to go further being 32 bit."
Also, they mention that with Nvidia propietary driver the game with full
setting doesn't go over 1.2 GB of ram (on my system, I detect a first peak of
almost 3Gb of ram usage before crashing). So, there is some way that Mesa
drivers could be leaking about 2Gb of ram? I understand that the memory usage
between propietary drivers a Mesa are quite different, but I feel that it's
quite suspicious that there is such a big ram usage for what seems to be
shaders compile output.
Finally, while running an apitrace I detected a lot this errors: "major shader
compiler issue 21156: 0:4(12): warning: extension `GL_EXT_gpu_shader4'
unsupported in vertex shader". Not sure if it could be related with any leak
though.
I'm attaching to the ticket my system information plus and the apitrace I got
until the crash. Let me know if there's any other information you need or if
it's necessary that I test this game with newer version of Mesa.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>