Running instruments agains the server version running it’s leaking around 25k 
every 10 seconds. The Leaks output is different on the server it says the 
responsible library is “CoreImage” and the responsible frame is 
“CI:GLTExtureManager::request_intermediate_for_node( CI::Node const*) 

the actual leaked objects are “_NSCFString”s and on the live device I”m loosing 
260 or so every 10 seconds to the tune of more than 25k each sampling period. 
If I stop passing any images into the core image stuff for processing then I 
don’t lose anything. 

It’s all over the place and different every time. Any recommendations for 
gathering some useful data? For all I know it’s a bug in core image itself, or 
that instruments isn’t reporting to me what I think it’s reporting. But the 300 
meg (now 320 since I originally posted) of compressed memory does tell me that 
something is leaking. It doesn’t do that at all if I just replace the core 
image stuff with a simple return and display the non-filtered image. 

I can send you the app for your own testing? Or save off an instruments 
document? All I know is that if I don’t actually create the Core Image then it 
works fine, if I do create a core image, even if I don’t process the image in 
any way just turn it into a CIImage and back again, it leaks. What can I do to 
gather more info?


> On Apr 14, 2016, at 3:17 PM, Christian Schmitz 
> <[email protected]> wrote:
> 
>> 
>> version on my server for the last 2 days and I’ve got about 300megs of 
>> compressed memory in the app now showing that it’s not been in use and just 
>> leaked and forgotten about.
> 
> 300 MB with 272 byte per leak? Sounds strange.
> 
> I run it 5000 times and lost 20 K and that'S difficult to debug.

Thanks,
 James


James Sentman                       http://www.PlanetaryGear.org                
http://MacHomeAutomation.com




_______________________________________________
Mbsplugins_monkeybreadsoftware.info mailing list
[email protected]
https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info

Reply via email to