<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - openGL glDeleteBuffers does not delete buffers created using glGenBuffers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65426#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - openGL glDeleteBuffers does not delete buffers created using glGenBuffers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=65426">bug 65426</a>
from <span class="vcard"><a class="email" href="mailto:brianp@vmware.com" title="Brian Paul <brianp@vmware.com>"> <span class="fn">Brian Paul</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=65426#c6">comment #6</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=65426#c5">comment #5</a>)
> > Is this really a problem? Mesa might not always reuse buffer names, but that
> > does not mean the buffer wasn't properly deleted. As far as I can see,
> > OpenGL does not require name reuse.
>
> It's standard compliant, but it sounds like a symptom of a leak.</span >
It's actually not a leak. glGenTextures/Buffers/Framebuffers(), etc call the
_mesa_HashFindFreeKeyBlock() function. For speed, it simply returns the next
previously unused integer. If we'd ever hit 0xffffffff (or whatever the new
hash table's limit is) we'd resort to searching the hash table for a lower,
unused ID. I doubt that any app/test has ever exercised that case though...</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>