<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Segfault vkCreateDescriptorPool in The-Forge on RADV"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110815#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Segfault vkCreateDescriptorPool in The-Forge on RADV"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110815">bug 110815</a>
from <span class="vcard"><a class="email" href="mailto:boberfly@gmail.com" title="Alex Fuller <boberfly@gmail.com>"> <span class="fn">Alex Fuller</span></a>
</span></b>
<pre>I managed to do some testing and I can now trigger the bug. It looks like when
creating a vkCreateDescriptorPool of size 11 which is the default
VK_DESCRIPTOR_TYPE_RANGE_SIZE everything is fine which is the behaviour I get
before. Because I updated the headers of Vulkan, the NV raytracing extensions
are now in the headers, and the size increases to 12 now in The-Forge codebase
from a preprocessor define. Their comment on this:
"//+1 for Acceleration Structure because it is not counted by
VK_DESCRIPTOR_TYPE_RANGE_SIZE"
So this segfault crash looks like there is some limit of
VK_DESCRIPTOR_TYPE_RANGE_SIZE when creating pools on RADV. Is there some
hardware limitation? ConfettiFX I am pretty sure are testing AMD's Vulkan
driver and haven't reported an issue afaik.
Cheers.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>