Hi,
First of all I appreciate this group very much for its informative discussions and posts.
Here is my question.
I have one process whose virtual memory size increases linearly from 6MB to 12MB in 20 minutes. Does that mean my process has memory leaks?
In what cases does the... (4 Replies)
I am running c++ code on AIX unix.I have a doubt that my code is using some memory but it is not clearing that.Some time i am getting heap allocation problem.In my code i am not using any malloc,new functions also i am justing using pointers and arrays.
Is there any way i can find out if the... (2 Replies)
I tried to execute a sample pthread program to cancel a newly created one using pthread_cancel(). but using valgrind on my code shows some memory leak.
My Code:
#include "iostream"
#include "unistd.h"
#include "pthread.h"
#include "signal.h"
using namespace std;
void handler(int);
void*... (4 Replies)
I have this code...
#include <stdio.h>
#include <iostream>
#include <pthread.h>
static void* cliente(void *datos);
int main()
{
pthread_attr_t tattr;
int ret;
size_t size = PTHREAD_STACK_MIN + 0x0100;
ret = pthread_attr_init(&tattr);
ret =... (8 Replies)
Hi.
This might be a strange request, but does anyone have any idea on a simple shell script that would use more and more memory as it ran? Like a purposeful leak.
I want to test the behaviour of an already running program when the machine runs out of memory.
Thanks! (4 Replies)
Hi All,
my client server application can work in two modes:
1) one direction - only client sends msgs to server
2) two directions - server gives 'answers' to client.
when program run in the first mode it looks OK, but when server answers to client than client's application exit its... (2 Replies)
Hi,
I am trying a database server which keeps a B+ plus tree structure and works on it.
I am trying to find the memory used/leak while executing this process.
I check the memory leak by using ps uax command.
When i execute a delete query i am sure that my code frees up the existing... (9 Replies)
I have written this code in C which reads a very large collection of text files and does some processing. The problem with this code is that there are memory leaks which I am not able to figure out as to where the problem is. When I run this code, and see the memory usage using top command, then I... (7 Replies)
Discussion started by: shoaibjameel123
7 Replies
LEARN ABOUT DEBIAN
memstat
MEMSTAT(1) Linux Programmer's Manual MEMSTAT(1)NAME
memstat - Identify what's using up virtual memory.
SYNOPSIS
memstat [-w][-p PID]
DESCRIPTION
memstat lists all accessible processes, executables, and shared libraries that are using up virtual memory. To get a complete list memstat
has to be run as root to be able to access the data of all running processes.
First, the processes are listed. An amount of memory is shown along with a process ID and the name of the executable which the process is
running. The amount of memory shown does not include shared memory: it only includes memory which is private to that process. So, if a
process is using a shared library like libc, the memory used to hold that library is not included. The memory used to hold the exe-
cutable's text-segment is also not included, since that too is shareable.
After the processes, the shared objects are listed. The amount of memory is shown along with the filename of the shared object, followed
by a list of the processes using the shared object. The memory is listed as the total amount of memory allocated to this object throughout
the whole namespace. In brackets also the amount that is really shared is listed.
Finally, a grand total is shown. Note that this program shows the amount of virtual (not real) memory used by the various items.
memstat gets its input from the /proc filesystem. This must be compiled into your kernel and mounted for memstat to work. The pathnames
shown next to the shared objects are determined by scanning the disk. memstat uses a configuration file, /etc/memstat.conf, to determine
which directories to scan. This file should include all the major bin and lib directories in your system, as well as the /dev directory.
If you run an executable which is not in one of these directories, it will be listed by memstat as ``[0dev]:<inode>''.
Options
The -w switch causes a wide printout: lines are not truncated at 80 columns.
The -p switch causes memstat to only print data gathered from looking at the process with the gicen PID.
NOTES
These reports are intended to help identify programs that are using an excessive amount of memory, and to reduce overall memory waste.
FILES
/etc/memstat.conf
/proc/*/maps
SEE ALSO ps(1), top(1), free(1), vmstat(8), lsof(8), /usr/share/doc/memstat/memstat-tutorial.txt.gz
BUGS
memstat ignores all devices that just map main memory, though this may cause memstat to ignore some memory usage.
Memory used by the kernel itself is not listed.
AUTHOR
Originally written by Joshua Yelon <jyelon@uiuc.edu> and patched by Bernd Eckenfels <ecki@debian.org>. Taken over and rewritten by Michael
Meskes <meskes@debian.org>.
Debian 01 November 1998 MEMSTAT(1)