On 09/08/16 02:21 PM, DRC wrote: > The primary reason the destructor exists is to free the shared memory > segment that VirtualGL uses for its GUI interface. Shared memory > doesn't get freed automatically.
If that were the only gotcha, the destructor could handle the shm segment only, with the GUI activation doing a single "am I dead" check. It would be nice if every new faker hook/resource access didn't have to remember about deadYet checks. The whole issue is pretty unintuitive from a code POV. "I said exit() what do you mean I'm not dead?" -Nathan ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
