<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - SIGBUS, Bus error during command buffer recording" href="https://bugs.freedesktop.org/show_bug.cgi?id=105509#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - SIGBUS, Bus error during command buffer recording" href="https://bugs.freedesktop.org/show_bug.cgi?id=105509">bug 105509</a> from <a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> Jason Ekstrand</a> <pre>(In reply to Vyacheslav from <a href="show_bug.cgi?id=105509#c4">comment #4</a>) > Workaround is to use one command buffer per frame (or per thread). Just > record everything inside primary command buffer. It is worse for performance > but it is better for mmap and it solved the problem. If you are using enough secondary command buffers to blow past the 1GB limit, then you are probably going to get garbage performance anyway. We have to do a full GPU on every vkCmdExecuteCommands so, while performance is probably fine if secondary command buffers are used sparingly, over-use of them can cause significant perf problems. I think there still is something of a driver bug here in that we really should be throwing VK_ERROR_OUT_OF_DEVICE_MEMORY instead of asserting or getting you int a situation where you can get SIGBUS.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>