FLIR One Developer / Blog / Topics / Class LoadedFrame in Android SDK probably causing native memory leaks

Class LoadedFrame in Android SDK probably causing native memory leaks

Home Forums FLIR ONE SDK Development Android development Installation and getting started Class LoadedFrame in Android SDK probably causing native memory leaks

This topic contains 0 replies, has 1 voice, and was last updated by Profile photo of Chi Chi 1 year, 6 months ago.

Viewing 1 post (of 1 total)

  • Author

    Posts

  • #6402

    Profile photo of Chi
    Chi

    Participant

    Hi,
    I am using FLIR One SDK v3 to develop an android application which needs to load multiple previously captured thermal images and convert them to visible light images by FrameProcessor in the sdk.

    However, I noticed that creating new instances of LoadedFrame with code like:
    LoadedFrame mFrame = new LoadedFrame(new File(“imagePath”));
    causing native heap keep increasing and never drops until application terminated.
    (And it consumes around 50MB if 10 images are loaded.)

    Could you please check if this is caused by the sdk?

    Thanks,
    Chi Chang

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.