linux-kernel - Question on Memory Leak: very tough problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALyraeOO2DHrS1oh0FLG11XuxEvMzgJ+MRRrxwXx+vLTxbuDYg@mail.gmail.com>
Date:	Wed, 26 Oct 2011 23:20:44 -0400
From:	Sri Ram Vemulpali <sri.ram.gmu06@...il.com>
To:	Kernel-newbies <kernelnewbies@...linux.org>,
	linux-kernel-mail <linux-kernel@...r.kernel.org>,
	kernelnewbies <Kernelnewbies@...nelnewbies.org>
Subject: Question on Memory Leak: very tough problem

Hi All,

I have very difficult problem I am working on to figure out where the
memory leak is in my system. Sometimes it shows up and sometimes it
reveals very slowly (I mean increments very slowly). This is dependent
on system load, if the system is in very high load, then leak is very
fast. We tried solving this problem from many dimensions, but no
success.

After quite sometime, we started using valgrind to capture the memory
leak. The funny thing is the leak disappears once we start running our
application on top of valgrind.
So, we cannot capture leak using valgrind. We came to conclusion that,
since valgrind serializes the allocations (leak disappears), we
thought this might be result of race conditions, that
resulted from system high load (by the way ours is multi threaded
system). We run system without valgrind we see the memory leak.

The question is, is it true that valgrind serializes the mem
allocations. Does this happen to anyone disappearing the leak when
used valgrind.

Any thoughts and input that can help me solve this problem. Thanks to
all in advance.

-- 
Regards,
Sri.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/