Alex Park <a...@nervanasys.com> writes: > Thank you for the response. > > As a followup question, I was looking at the underlying code for > ipc_mem_handle, and it seems like when a handle is deleted, it tries to do > a mem_free on the underlying device pointer. > > So could there not be a situation as follows: > > 1. Process A allocates gpuarray G and passes IPC handle H to Process B > 2. Process B unpacks H, does something with it, then lets it go out of > scope, so H is closed and the underlying gpu mem is freed > 3. Process A then tries to do something on G but then finds that its > memory has already been freed
Hum, sounds like that needs to be fixed. I'd be happy to take a pull request. Andreas
signature.asc
Description: PGP signature
_______________________________________________ PyCUDA mailing list PyCUDA@tiker.net http://lists.tiker.net/listinfo/pycuda
