That "300 bytes" sounds familiar. :-)<div>I have also seen this before. <div>According to this, <div><br></div><div><a href="http://lists.mcs.anl.gov/pipermail/petsc-users/2011-December/011690.html">http://lists.mcs.anl.gov/pipermail/petsc-users/2011-December/011690.html</a></div>
<div><br></div><div>I think it has something to do with OS and not important. </div><div><br></div><div>Best, </div><div>Mohamad</div><div><br></div><div>Mohamad<br><br><div class="gmail_quote">On Wed, Feb 15, 2012 at 1:32 AM, Mohammad Mirzadeh <span dir="ltr"><<a href="mailto:mirzadeh@gmail.com">mirzadeh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>This might just not be important but I'm still curious about it. When I run valgrind on this:</div>
<div><br></div>int main (int argc, char **argv){<br><br> PetscInitialize(&argc, &argv,(char *)0,help);<br>
PetscFinalize();<div><pre style="margin-top:0px;margin-bottom:0px"></pre></div><div><br></div><div> return 0;</div><div>}</div><div><br></div><div>I get,</div><div><br></div><div><div>==7262== HEAP SUMMARY:</div><div>
==7262== in use at exit: 300 bytes in 11 blocks</div><div>==7262== total heap usage: 203 allocs, 192 frees, 643,759 bytes allocated</div><div>==7262== </div><div>==7262== LEAK SUMMARY:</div><div>==7262== definitely lost: 60 bytes in 1 blocks</div>
<div>==7262== indirectly lost: 240 bytes in 10 blocks</div><div>==7262== possibly lost: 0 bytes in 0 blocks</div><div>==7262== still reachable: 0 bytes in 0 blocks</div><div>==7262== suppressed: 0 bytes in 0 blocks</div>
<div>==7262== Rerun with --leak-check=full to see details of leaked memory</div></div><div><br></div><div><br></div><div>Is this normal?</div><div><br></div><div>Thanks,</div><div>Mohammad</div><div><br></div></div>
</blockquote></div><br></div></div></div>