I'll also submit this to RS feedback. In the absence of a way to definitely prove whether it is the plugin, the cocoa framework, or some combination that is creating the leak, I fear this will become a case of developers pointing at the other person.
I tried analyzing using Apple's developer Instrument but that did not help detect nor identify the leak. We'd need a tool that can identify which blocks are persisting and which process/routing allocated them. On Sep 3, 2012, at 3:26 AM, Christian Schmitz <[email protected]> wrote: > > Am 03.09.2012 um 04:18 schrieb Guy Kuo <[email protected]>: > >> If you are using QTgrabberMBS under cocoa, please check your app's memory >> utilization after several minutes or hours. We are seeing a slow memory leak >> in Cocoa builds. > > > I don't think this is a plugin issue. More likely a leak in RS's cocoa > runtime. > > <feedback://showreport?report_id=22412> > <feedback://showreport?report_id=22413> > > > Greetings > Christian > > -- > Check out the Omega Bundle: > > http://www.omegabundle.com/ > > _______________________________________________ > Mbsplugins_monkeybreadsoftware.info mailing list > [email protected] > https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info > _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
