CGRU Forum

I am not able to get it to crash ....

or maybe you can give me a good hint on how to properly attach valgrind so we have more debug info.

did you get around to dig into this? It is getting annoying.

Often I get the question from artists: "My job does not get a renderclient! Whats wrong?" Most times it can be solved by looking at the various parameters of the job "prio, creation date, hostmask, ram, lics, capacity". It would be really helpfult if a block had a data filed with...

We have about 200 dedicated rendernodes and 40 workstations with 25 monitors. But as soon as I add the 40 workstations afserver starts to spit weird glibc double free errors.... We had trouble with afserver crashing before but it was never so obvious. It's hard to debug in full production right now ...

It seems it is happening here after a while if I add all workstations to the farm. If I add the workstations to a separate server all is fine with them and no crashes.
@lithorus: How many clients are online at your place?

This is a standard CentOS 6.6 with gcc 4.4.7

The valgrind and the crash backtrace are different. Will test more.

signature updated

Btw, we are using the latest version. Today I used Valgrind for the first time. Like this: valgrind --tool=memcheck --leak-check=yes afserver Is it normal for Valgrind to detect so much leaked memory even when there is no work and no render connected? ==28879== ==28879== HEAP SUMMARY: ==28879== in u...

The server has 16GB of RAM and normally only 3-4GB are used for real. But the cached/buffered part was nearly maxing out the RAM when I checked the last time. But I think the Linux OS frees the cached part if is needed or not?

Another question is:
as far as I know (and per http://www.cplusplus.com/reference/new/operator%20new[]/) the new operator never returns a NULL pointer. Why do you check it like this. Wouldn't it be good to use a try: catch: ??