On 5/4/21 23:44, Derek Lesho wrote:
The problem is not with the graphics APIs closing the handles they use to get the FDs or the shared memory handles, the problem is with the user code closing the shared memory object and wine having no way to know how to release the reference that now-destroyed shared memory holds to the fd object. This also assumes that there is a indeed a way to hold a global reference to the fd object from the shared memory, which I don't think there is.
Yes, indeed, at least my limited (to say the least) involvement into this problem doesn't allow me to see such a solution. Yet it looks a bit weird me to introduce a whole driver taking a separate process and acting just as a placeholder for handle and shared object. Are you sure there is no good way to add some support to wineserver (maybe keeping away some specific 3D details from it)?