search for: leake

My Valgrind doesn't run, saying it doesn't support showing more than 50 entries of a stack trace --- test/test_bins.sh | 4 ++-- test/test_flac.sh | 8 ++++---- test/test_grabbag.sh | 8 ++++---- test/test_libFLAC++.sh | 2 +- test/test_libFLAC.sh | 2 +- test/test_metaflac.sh | 12 ++++++------ test/test_seeking.sh | 12 ++++++------

...Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Event 0x827d6e20 leaked (parent=0x827d4220): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x827d6420 leaked (parent=0x827d4820): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x82780c20 leaked (parent=0x827d6220): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x827d6c20 leaked (parent=0x827...

First, I'm not sure if deleting the ExecutionEngine is all I need to clean-up... so I started with a minimal test just to check int main( int argc, char **argv ){ while( true ){ Module *M = new Module("M"); Function *F = cast<Function>(M->getOrInsertFunction("F", Type::Int32Ty, (Type*)0)); BasicBlock *BB = new

Hello *, I'm running dovecot 1.0.10 on a Fedora 6 with this configuration # 1.0.10: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/dovecot/etc/mailbox.pem ssl_key_file: /usr/local/dovecot/etc/mailbox.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default):

...ive.ee>> wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> >>>>> Noticed with latest v2.3.3 some new warning in logs, for example: >>>>> >>>>> dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)): >>>>> auth-client-connection.c:338: 1 Time(s) >>>>> dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)): >>>>> auth-client-connection.c:338: 1 Time(s) >>>>> dovecot: auth: Warning: Event 0x80aa718 leaked (parent=...

...; <div> <br> </div> <div> <br> </div> <div> Noticed with latest v2.3.3 some new warning in logs, for example: </div> <div> <br> </div> <div> dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)): </div> <div> auth-client-connection.c:338: 1 Time(s) </div> <div> dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)): </div> <div> auth-client-connection.c:338: 1 Time(s) </div> <div>...

One of the Mozilla developer released a new extension to detect JS memory leaks: https://addons.mozilla.org/firefox/2490/ If it''s accurate, it might be bad news for Prototype. I have some code using prototype 1.4 with no leaks, but other code with 1.5 leaks on every single bindAsEventListener call, and a bunch of other places. Not sure if it''s just me; I may just be

I am going through my maillog file, and noticed these events: Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event 0x55db5bc41200 leaked (parent=0x55db5bc3b830): mail-storage-service.c:1325 Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event 0x55db5bc3b830 leaked (parent=0x55db5bc34450): smtp-server-recipient.c:38 Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event 0x55db5bc34450 leaked (parent=0x55db5...

On Sun, 15 Jul 2007, Paolo Invernizzi wrote: > First, I'm not sure if deleting the ExecutionEngine is all I need to > clean-up... so I started with a minimal test just to check Is this llvm 2.0 or llvm svn head? Several minor memory leaks have been fixed since llvm 2.0. -Chris > int main( int argc, char **argv ){ > while( true ){ > Module *M = new

Hello, While working on lld code, I encountered a couple of memory management issues. If lld should be usable as a library, I assume it should not leaks any memory when performing a single link pass (UniversalDriver::link(arc, argv)). Actually, after calling that function, I got some major leaks. I may be wrong, but I think there is 3 major leaks. - One of the main leak is in FileArchive. When

...e > > > <mailto:sysadmin at e-positive.ee>> wrote: > > > > > > > > > Hi, > > > > > > > > > Noticed with latest v2.3.3 some new warning in logs, for example: > > > > > > dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)): > > > auth-client-connection.c:338: 1 Time(s) > > > dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)): > > > auth-client-connection.c:338: 1 Time(s) > > > dovecot: auth: Warning: Event 0x80aa718 leaked (parent=(nil)): > > > a...

...ysadmin at e-positive.ee <mailto:sysadmin at e-positive.ee>>> wrote: >>> >>> >>> Hi, >>> >>> >>> Noticed with latest v2.3.3 some new warning in logs, for example: >>> >>> dovecot: auth: Warning: Event 0x80a6fc0 leaked (parent=(nil)): >>> auth-client-connection.c:338: 1 Time(s) >>> dovecot: auth: Warning: Event 0x80aa1c8 leaked (parent=(nil)): >>> auth-client-connection.c:338: 1 Time(s) >>> dovecot: auth: Warning: Event 0x80aa718 leaked (parent=(nil)): >>> auth-client...

...ed. Heck, even the bugs that we've fixed might not > have existed two years ago (I've certainly created (and > fixed) my share of bugs in debug info). > > Best you start with a leak tracking tool and at least be able to point to the > major leak culprit (eg: "90% of the leaked memory was allocated at <stack > trace>") > > On Fri, Jun 13, 2014 at 9:16 AM, Sergei Larin <slarin at codeaurora.org> wrote: > > > > David, (and everyone else) > > > > I am forced to do some maintenance work on a fairly old LLVM branch > &gt...

By default valgrind suppresses many leaks. I'm not even sure exactly how it decides which ones to suppress, but certainly global variables pointing to malloc’d data are suppressed, which is not useful behaviour. Tell valgrind to show all leaks. It won't give an error on them. However to do this we also need a much more comprehensive list of suppressions so that we don't constantly

I am running a very simple multithreaded program (TestThread.C) which calls gethostbyname_r in several threads. My analysis of this program with both truss and DTrace suggest that is has a small leak. However, if I alter the program to have many more threads and run for a lot longer it never runs out of memory and does not carry on growing. Can anybody explain what I am missing in my analysis or

...s is not constantly being shutdown and/or restarted and Dovecot is used for SMTP authentication (Postfix). Checked few servers logs, they are running v2.3.3, for example latest (some day none, some day a lot, some day few) logs: Nov 25 18:48:11 server1 dovecot: auth: Warning: Event 0x2b79250f15f0 leaked (parent=(nil)): auth-client-connection.c:338 Nov 25 18:48:11 server1 dovecot: auth: Warning: Event 0x2b79250ddc50 leaked (parent=(nil)): auth-client-connection.c:338 Nov 25 22:55:38 server1 dovecot: auth: Warning: Event 0x2b374a7bafb0 leaked (parent=(nil)): auth-client-connection.c:338 Nov 26 03:0...

Holger. > You can find out what exactly leaks with the help of valgrind. It seems, that Paolo is on Mac OS X. No valgrind there :( -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

On 2007-07-14, at 13:56, Anton Korobeynikov wrote: >> You can find out what exactly leaks with the help of valgrind. > > It seems, that Paolo is on Mac OS X. No valgrind there :( All is not lost… http://developer.apple.com/documentation/Performance/Conceptual/ ManagingMemory/Articles/FindingLeaks.html — Gordon

...ure (http://llvm.org/bugs/show_bug.cgi?id=18320), > > all of which are easy to fix. > > And there are also lots of leaks in TableGen. I think the problem with TableGen is that we call leak checking too late - after the global destructors, not before them. IIRC pointers to objects "leaked" in TableGen are stored in a set with static storage duration. If we're able to call __lsan_do_leak_check() right after main(), we will treat that objects as reachable. I considered adding a call to __lsan_do_leak_check into llvm_shutdown() function, but that looks wrong - for instance,...

Hi, I'm currently trying to find and fix memory leaks (compiling with ``-fsanitize=address``) in the KLEE tool [1] an having found some leaks and I'm having trouble suppressing them. I'm trying to suppress them using the ``-fsanitize-blacklist=blacklist.txt`` option as documented at [2]. I'm using Clang 3.7 ( Arch Linux package 3.7.0-6). The sort of reported leaks I see are ```