Hello Marek,
this was time and nerve consuming (with all the LLVM 11
revert/re-revert).
FreeCAD vbo rendering bugs.
Mesa-20.1-rc4 is fine (sure)
Mesa git with #2840bc3065b reverted (glthread_draw.c deleted), too.
/opt/mesa> git bisect bad
2840bc3065b9e991b2c5880a2ee02e2458a758c4 is the first
> What are the exact use-cases for Mesa specific allocation data?
In general, the use case is to implement Vulkan allocation callbacks.
Our particular use case is memory accounting: there is a fixed memory budget,
so we need to keep track (not as an external tool but in the application
itself)