When I last looked at the local surface pool, it had a FusionCall. This is because in multi-app the Master process deletes surfaces and the local surface pool allocations are in the process space of the Slave. The FusionCall allowed a synchronous way for the underlying memory allocation of the surface to be freed before the surface object was deleted.
However as part of the final secure fusion check-in, this FusionCall was removed (check-in: ee5bad2be947b14e4b5eb5ff5b6e247ae38b4c17). How does the master now signal to the slave to delete the allocation? Thanks, Bryce
_______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
