On 07/07/16 06:01 PM, DRC wrote: > I'll need to sit down and focus on this when I have no distractions, > because it raises a couple of red flags in my mind. Stand by.
Some things I mulled over, not long enough or distraction-less enough: 1. this no longer blocks any globalMutex-checking caller from using VGL resources during cleanup() 2. but XFree() is the only call, besides (newly) xcb_poll_for_event() attempting to use this guard for resource access and they're both via isDead() which will do the right thing (i.e. not access if dead) 3. which makes me think about whether we need isDead protection for all resource access (since _fini() proves we aren't dead just because we said exit(1). But that way seems cumbersome and non-performant, not to mention and the way of more potential deadlocks. Worthy of a long think indeed. /me returns to other distractions ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
