I find temporal solution with help from radasol he told me that ver 6801 is rock solid, i try it and results appear. No memory eat no cpu consumption and all is without any changes in settings. Older version is attached bellow.
Update:
Also checked with newer 7179 also work fine i think the problem is after 7183
The attached patch reverses suspicious changes that happened after 7179. Please apply it and test to see if there is memory leak.
I have started from the diff between 7179 and current trunk and left only the relevant (IMO) part. To apply the patch, save it oscam source directory and run: patch -R -p1 < test_patch.txt
test_patch.txt
Unfortunately looking at the patch I see nothing that should cause the severe memory leaks that you are seeing.
Hi gtfo. I was testing 7135 and memory leak was very severe. 80% of all RAM(2GB) was used by OScam after 1 day and 8 hours of operation. I am using camd35, cacheex, cccam and newcamd. Nothing special.
Now iam running 7180 and i yet have to see if there are memory problems. I also have to say that newest versions are unstable. They maybe work for a hour or two and then crash. I tried debugging with gdb but oscam behaves differently then. Not all clients can connect to me, not sure why!
Well, cacheex is a lots and lots of code sticking its fingers almost everywhere and cccam is no better :)Originally Posted by PlatoonRTV
I am also having memory problems. My 2GB ram is filled within one hour, then oscam crashes. (no specific error is shown in the default log).
My environment:
Hardware: Proliant DL380 with vmWare / Oscam virtualized 2 [email protected] / 2GB RAM
Kernel: Linux VPS4398 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Oscam: 1.20 build 7224
Protocols: CC-Cam, Camd35, newcamd
Normal readers/users: 30/30
Cache-Ex readers/users mode 3: 25/25
I have these problems since a month or so, will try to revert to version 7179 as mentioned above.
I don't have a clue how to debug this, any help is appreciated.
Thx!
8180 also seems to be good. Please report.
I think you mean 7180 ? :)
I think changes in camd35 maybe is the reason. Because some of my peers can`t connect to me with newer oscam via camd35. There is a lot of changes on camd35 after 7179.
Unlikely, the changes are very small and all of them are fixes for possible crashes.
gf@gf:~/git/oscam$ git log --oneline f550a53f1f4e00c92b697d031369fbd36e34cf10 .. module-camd35.c
a7aafe2 fixed a emm-camd35 segfault
abdb1b4 camd35: fixed an aes segfault when using cacheex with camd35
f550a53f1f4e00c92b697d031369fbd36e34cf10 is svn 7179
The easiest way to detect memory leaks is to use valgrind. See this http://streamboard.de.vu/wbb2/thread.php?threadid=31968
Posting Permissions
