[Mono-bugs] [Bug 72792][Maj] Changed - mono eats memory running on SLES

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 4 May 2005 03:58:38 -0400 (EDT)


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by andreas.weiss@de.bp.com.

http://bugzilla.ximian.com/show_bug.cgi?id=72792

--- shadow/72792	2005-05-01 16:21:25.000000000 -0400
+++ shadow/72792.tmp.11616	2005-05-04 03:58:38.000000000 -0400
@@ -417,6 +417,26 @@
 
 ------- Additional Comments From bmaurer@users.sf.net  2005-05-01 16:21 -------
 This valgrind shows no leaks at all.
 
 Valgrind is going to cause it to use lots of extra memory, but just
 let it run for a few hours; your test run feels very short.
+
+------- Additional Comments From andreas.weiss@de.bp.com  2005-05-04 03:58 -------
+It is unbelievable but using valgrind didn't my filecopy-application 
+leaks. I didn't repeat it more than twice because it was to much for 
+my little brain.
+
+I run valgrind over 2 days with my httpget.exe application and it 
+leaked after nearly 24 hours. 
+==7777== LEAK SUMMARY:
+==7777==    definitely lost: 2514296 bytes in 17000 blocks.
+==7777==    indirectly lost: 317995 bytes in 2177 blocks.
+==7777==      possibly lost: 100356 bytes in 670 blocks.
+==7777==    still reachable: 6540551 bytes in 42032 blocks.
+==7777==         suppressed: 0 bytes in 0 blocks.
+
+a memory usage diagram = valgrind_httpget.exe.bmp
+a valgrind log = valgrind_httpget.exe.log
+
+a note: We don't have any pressure to fix the leak because I had to 
+gave up and another company got the job. Don't worry about.