Huge memory consumption with CACHE-EX

[htcX]

Maybe you still had in the air oscam active, so init of local cards didnt go well
just kill all oscam processes and restart oscam

killall -9 Oscar
then restart as usual

my debian feels very good now after I did limitations on mem and virtual mem
after 3 hours + 20 min stats say this:

top - 03:36:05 up 17:18, 4 users, load average: 0.00, 0.00, 0.00
Tasks: 122 total, 1 running, 121 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.2%us, 1.2%sy, 1.2%ni, 96.9%id, 0.0%wa, 0.3%hi, 0.3%si, 0.0%st
Mem: 3340756k total, 1273160k used, 2067596k free, 808788k buffers
Swap: 3203064k total, 0k used, 3203064k free, 362964k cached


PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11982 root 39 19 68812 17m 1716 S 4 0.5 10:26.09 oscam


cheers

[CyberCrime]

My server auto downloads and install the latest oscam everyday and i just seen that todays update 7231 as not got the memory bug.
After 7 hrs i have used 225meg.

[CapNCooK]

Here's a little update on my memory problems with cache-ex.

For me, this problem rised in build 7191. Seen from the Oscam Timeline, update 7191 contains a cache-ex modification by 'Corsair'.
-> http://streamboard.de.vu:8001/changeset/7191

The next update from this user, in build 7195 has description: 'cacheex: fixed my last commit (memleak)'
-> http://streamboard.de.vu:8001/changeset/7195

Strange enough, i think this problem was never fixed properly, because i have this problem in every version from 7191 upto the latest build.

--

I'm currently at build 7190, having 0 memory issues after 4 hours run.
-> 18904 oscam 39 19 544m 18m 1472 S 5.3 0.9 1:41.30 oscam
As soon as i update to 7191, or any other later version the memory starts rising quickly, and make oscam crash.

--

To anyone still having this problem, can you check and confirm that:
- Build 7190 is stable for you
- Build 7191 is not
- Build 7195 doesn't fix the leaking

If a few users report positive, we can file an official bug in the Oscam tracker.

Thanks!

[gfto]

Guys, the only way this can be fixed if somebody provides valgrind log of the oscam that leaks. Once I have the log it would be couple of minutes work. I have given the link how to do that couple of posts before this one.

[CapNCooK]

Guys, the only way this can be fixed if somebody provides valgrind log of the oscam that leaks. Once I have the log it would be couple of minutes work. I have given the link how to do that couple of posts before this one.

valgrinding now..

[CapNCooK]

Executed valgrind as suggested on Oscam build 7229 on Ubuntu 12.04 x64 with 2GB ram.

Consistent high CPU load (> 50%) is noticed, and i let the memory increase until 15.0, then shutdowned.
(in build 7190 it consumes about 1.1 / 5% cpu)

I exececuted with: valgrind -v --leak-check=full --show-reachable=yes --error-limit=no --undef-value-errors=no --log-file=valgrind.log ./build/oscam -b -r0
See the log here: http://pastebin.com/LU6sMJq7

Thanks

[turbopower]

With #7237 is present

[CapNCooK]

With #7237 is present

I know, but it's the same thing from > 7191

[gfto]

Executed valgrind as suggested on Oscam build 7229 on Ubuntu 12.04 x64 with 2GB ram.

Consistent high CPU load (> 50%) is noticed, and i let the memory increase until 15.0, then shutdowned.
(in build 7190 it consumes about 1.1 / 5% cpu)

I exececuted with: valgrind -v --leak-check=full --show-reachable=yes --error-limit=no --undef-value-errors=no --log-file=valgrind.log ./build/oscam -b -r0
See the log here: http://pastebin.com/LU6sMJq7

Thanks

Unfortunately the log is from oscam compiled without debug information and thus is not useful :(.

Please, compile oscam by running

make DEBUG=1 OSCAM_BIN=oscam-dbg

in the oscam source directory and then run

valgrind --leak-check=full --show-reachable=yes --error-limit=no --undef-value-errors=no --log-file=valgrind.log ./oscam-dbg -b -r0

[turbopower]

My server auto downloads and install the latest oscam everyday and i just seen that todays update 7231 as not got the memory bug.
After 7 hrs i have used 225meg.

Tested with this version and but memory leak is present but it slow step in increasing. I will see how much time will be online.

P.S. In may case after 15 min online all my ram is gone and after that crash.