FW: initWithAPI / dealloc pairing quesiton.
FW: initWithAPI / dealloc pairing quesiton.
- Subject: FW: initWithAPI / dealloc pairing quesiton.
- From: Peter Litwinowicz <email@hidden>
- Date: Fri, 06 Mar 2015 12:38:50 -0800
- Thread-topic: initWithAPI / dealloc pairing quesiton.
The app terminates, and the OS frees up the remaining memory including the instance that was in the project. Its -dealloc method will never be called.
This is now major issue for us, because the FCP/Motion assumption that all we are doing in the plugin is freeing up memory is not a valid assumption. We also need to free up some global state and resources for the machine that are global to the state of the machine, and not whether the app is running or not (this pertains to our license counting mechanism, but could also apply to shared memory, and other items). Okay, you say… just release things when the app quits.
All is well and good, unless those shared system state and resources are moved to an XPC service as provided by FxPlug v3. If dealloc is never called, we can never tell that service to release the system resources we are holding on to. Worse, it seems the XPC service is killed with something like SIGKILL without calling our singleton C++ destructors and other registered items to be called upon exit, so the system resources get left dangling in the wind.
Filing bug now. Pete
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden