This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux memory leak

Other Parts Discussed in Thread: OMAPL138

Hi,

In my OMAPL138 application I've noticed increased memory use in category Active(file). I've tried to google this but haven't any reasonable explanation.  mcsdk_1_01_00_02 and syslink_2_21_01_05 are in use. Any dynamic structures, object creation etc. which might cause this are not used. A number of files, about 40, are now-and-then opened, updated and closed. Values in table below app is running. Application will die in some 12h when there still is tens of megs free memory??

I understand that it is impossible with this information point the exact reason but I would appreciate a hint where to try to find....

risto

  • Hi Risto,
    Able to see the same behavior in TI EVM board (LCDK, Zoom, SDI) ?
    It seems to me that problem is not due to kernel or board, its from application.
    I have also seen this behavior when we open the files and not closing in proper order and we could get the problem like this so please check the application part.

    Are you not getting this problem (memory) when you are not running the application ?

  • Hi Shankari,

    I agree, problem is in application, memory use does not increase if application is not running. We open-append-close relatively large text files which seems to leave some garbage to the memory. I do not have EVM available and I'm afraid it would not help as my HW is compatible with LCDK.

    About Active(file) google found: "is likely referring to the File Cache which contains disk and network filesystem data and metadata (can include files loaded into memory and possibly execution code from disk?)."

    I did not find any cleaning "tool" to run to reduce Active(file) now-and-then - this would be strategy B as it seems to be impossible to prepare this in app code - everything has been tested :-(

    We are running 4 parallel threads and in one of them a notify from DSP is lounching this file operation - I wonder if we should protect this open-modify-write with mutex or GateMP, I will try if any influence?

    risto