Hi, I have a problem with a deamon process that I have written. It is listening some text commands on a local socket and does some background job. I am using the same executable to send commands to the deamon process. What I observe is that it crashes after some time and it is only when RSS size reaches 65500K. I suspected of a heap problem at first and i have used valgrind to track memory issues. It helped me to find some minor memory leaks but it didn't affect much. Later I have written a logging method to log current memory usage when called as below: void getMemoryUsage(char *position) { char result[BUFFER_SIZE + 1]; char* command = "ps -eaf | grep BSM | grep -v grep | awk '{print $2}' | xargs ps -ly -p | tail -1"; FILE* ptr; pthread_mutex_lock(&mutex_mem); if ((ptr = popen(command, "r")) != NULL) { fgets (result, BUFFER_SIZE, ptr); int len = strlen(result); result[len - 1] = '\0'; log_debug("|%s||%s|\n", position, result); } pthread_mutex_unlock(&mutex_mem); pclose(ptr); } Sample output for this is: [2010-01-28 12:31:19.162] |::loop1::||S 0 13967 1 0 80 0 944 5170 pipe_w pts/1 00:00:00 limit| What i recoginezed is that the RSS value increases in each different method call by 4K in the first call only. For example in the following command RSS increases by 4K but only in the first time. When it is called again RSS does not change: char* end_of_command = strchr(message, KEY_SOCKET_SEPERATOR); This is almost the same for every other method type. So I thought that it is because of the stack increase in each call or something. The problem is that RSS usage never drops when a method returns and keeps increasing in each call thus reaching near 65M and program crashes. Does anybody have a clue on what might be causing that weird behaviour? Thanks in advance. -- To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html