search

thaolt / qscite

Automatically exported from code.google.com/p/qscite
GNU General Public License v2.0
0 stars 0 forks source link

Memory Leaks #39

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
The Valgrind report shows the following:

==5380== 
==5380== HEAP SUMMARY:
==5380==     in use at exit: 1,629,470 bytes in 20,478 blocks
==5380==   total heap usage: 284,037 allocs, 263,559 frees, 42,266,629 bytes 
allocated
==5380== 
==5380== LEAK SUMMARY:
==5380==    definitely lost: 4,784 bytes in 20 blocks
==5380==    indirectly lost: 78,640 bytes in 1,009 blocks
==5380==      possibly lost: 1,129,331 bytes in 13,180 blocks
==5380==    still reachable: 400,635 bytes in 5,984 blocks
==5380==         suppressed: 16,080 bytes in 285 blocks
==5380== Rerun with --leak-check=full to see details of leaked memory
==5380== 
==5380== For counts of detected and suppressed errors, rerun with: -v
==5380== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 297 from 16)

We need to make sure that destructors are implemented correctly.  Also we need 
to make sure that our classes are in Cannonical Form (Copy Constructor, 
Destructor, and overloaded assignment operator) for all that use heap based 
memory.  The -Weffc++ flag would help but the QT libraries appear to have lots 
of problems.

Original issue reported on code.google.com by didoro...@gmail.com on 2 Oct 2010 at 3:48