OOM Killer in DM368

Leon Pollak

Hello, all.

We have our DM368 application based (but reworked) on UDWorks reference design. It runs recording 2 video channels for hours, but suddenly the OOM Killer jumps out and kills the application. This may happen after 4 hours or after 40min.

In order to determine the error source we set /proc/sys/vm/overcommit_memory=2, which should actually forbid overcommitments. We expected to see some malloc() to be not satisfied, or something similar. And yes, the tests done showed malloc() returning zero.

BUT!!!!! When we run the application, still Killer jumps out occasionally!

Can somebody give us ANY(!) hint what to do and where to look for?

Thousands of thanks ahead.

over 14 years ago

0 timothybean over 13 years ago

Expert 1010 points

I am seeing the same issues. I am using grstreamer from API though... What did you do to resolve this?

Thanks

Tim

0 Leon Pollak over 13 years ago in reply to timothybean

Intellectual 960 points

You are lucky - I spent several weeks to solve this.

In brief - issue the following commands to solve this:

sysctl -w vm.overcommit_memory=2
sysctl -w vm.overcommit_ratio=90
sysctl -w vm.dirty_ratio=10

For the help search Internet for these parameters.

Regards

0 timothybean over 13 years ago in reply to Leon Pollak

Expert 1010 points

Thanks so much for the info. Is this a command that needs to be run every time at boot or just once?

Thanks

0 Leon Pollak over 13 years ago in reply to timothybean

Intellectual 960 points

I strongly recommend you to read about the commands, as the numbers I put are suitable for my case - yours may be different.

I put them into the start script.

Processors

Processors forum

OOM Killer in DM368