Hi,
The segfault line from the kern.log: segfault at 7f7300000080 ip 00007f7300000080 sp 00007f739fffca18 error 15
We’ve seen several core dumps in the glDeleteBuffers call.
Here’s a stack-trace after our application:
#0 0x00007f13c0bcc400 in ?? ()
No symbol table info available.
#1 0x00007f14894f8383 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40
No symbol table info available.
#2 0x00007f14894f7f4f in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40
No symbol table info available.
#3 0x00007f1489484cbd in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40
No symbol table info available.
#4 0x00007f148948530e in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40
No symbol table info available.
#5 0x00007f14894857d8 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40
No symbol table info available.
#6 0x00007f148907fd45 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.430.40
The calls to glDeleteBuffers are between our rendering cycles, I suspect that there’s a bit of allocation/de-allocation calls performed around the the segfault. I expect it’s something I’m doing, or have missed.
Thanks for your time,
Mark
nvidia-bug-report.log (2.0 MB)