possible native memmory leak

[wseemann]

possible native memmory leak

[wseemann]

Fixed in the latest release, version 1.0.11.

[danielmoraes]

I noticed this same issue on the most recent version of the library.

[MohHeader]

me too :(

[denite]

Ditto... Any way to get around this?

[Filimindji]

Hi,

I have done some research about that. It look like that the native JNI library should be unloaded when the classloader which loaded the library is garbage collected. (according to http://stackoverflow.com/questions/453359/how-to-unload-library-dll-from-java-jvm)

I was hopping that this operation can "resolve" the memory leak. But it don't.

I did a really simple app that do that in a loop :

FFmpegMediaMetadataRetriever mmr = new FFmpegMediaMetadataRetriever();
mmr.setDataSource(desc);
mmr.release();

After ~220 iteration, the app crash.

[wseemann]

I've looked into this issue and I'm not sure there is a way around it. Android loads FFmpeg each time you create a new instance of FFmpegMediaMetadataRetriever and calling release() doesn't seem to unload the references. I've spent a fair amount of time looking into this issue and I haven't found a solution. As a workaround, it's not necessary to create a new instance of FFmpegMediaMetadataRetriever each time you call setDataSource. Perhaps you should try reusing the same FFmpegMediaMetadataRetriever instance until you have extracted metadata from all the files and then call release() only once.

[Filimindji]

Thank you for the feedback.

I think You are right. As a workaround I don't execute my code in a loop, but less frequently after a specific user action.

Now the garbage collector have more opportunity to really release the memory, and my app do not crash anymore.

I think your advise to create only one instance of FFmpegMediaMetadataRetriever is wize. But in my case, the code is placed into an android plugin called by a C# method into an unity project (my interop skills just reach a new level :) and I prefer to avoid multi-thread synchronization and thread safety issue, if any.

[tonggang1308]

This issue still is exist at version 1.0.11!

[zjupure]

still memory leak in native