On Aug 9, 2012, at 15:05 , Charlie Dickman <3tothe...@comcast.net> wrote:
> I tried the Speech Synthesizer Manager too. It suffers from the same > deficiency that NSSpeechSynthesizer does. I suspect that NSSpeechSynthesizer > uses the Speech Synthesis Manager internally. One alternative, if you're targeting 10.7+, is to use XPC instead of NSTask. That would allow you to have 2 processes *and* control both ends with your own code. By sealing your use of NSSpeechSynthesizer in a separate XPC process, you can isolate the memory leak to the address space of a process that can and probably will terminate when idle. In addition, with XPC it should be fairly easy to control which part of your data is spoken and when. At least, that would be the theory. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
