I think I figured out what was happening, It takes hours of running the stream to make sure that it’s happening or if it's just going to build to some equilibrium with the auto release pool at a new higher level. The version I left running over night did stabilize and stopped adding memory, and the version I am running this morning is also working fine apparently, but it’s only been running for a couple of hours. The only change I made was to turn the verbose flag off in the initial arguments you pass to VLC. I had turned it on previously and that might be what was slowly building in memory since I was never reading it out anywhere? In the last hour the memory allocation has increased only another meg and we haven’t yet reached the point at which the overnight version stopped needing any more so I’m still watching but that might be the answer. Previous versions would leak hundreds of megs over the course of the day, my overnight stream topped out at only 88 meg and about 12 meg compressed. This one has currently reached 78.3 but is growing much more slowly. I continue to watch it.
I’ll post again if I can’t duplicate this lack of leak. It is weird that I can’t seem to connect instruments to it without crashing it though. That would have been helpful in figuring this out. Thanks Christian! James > On Dec 8, 2017, at 2:54 PM, Christian Schmitz > <supp...@monkeybreadsoftware.de> wrote: > > Well, I tried normal playback. > > Not sure if VLC builds a cache there or you run a different code path than > me. I don’t see a problem here right now. > >> Since I really only need to capture frames from it and don’t need to display >> it in realtime I experimented with not linking it to the CGContext of the >> window and just capturing frames via copyPicture. That didn’t change >> anything, so instead I disabled the call to copyPicture and only left it >> playing in the window but that also didn’t change the memory expansion. So I >> don’t think the problem is with the copyPicture function, or at least not >> only with the copyPicture function. > > Is that a specific Xojo version, oder plugins? > > I don’t see it here on my Mac. > You can use instruments and check which functions allocate a lot of memory. Thanks, James James Sentman http://www.PlanetaryGear.org http://MacHomeAutomation.com _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list mbsplugins@monkeybreadsoftware.info https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
