Página inicial Explorar Ajuda
Registrar Entrar
FIX
/
MIVAS
3
0
Fork 0
Arquivos Issues 0 Pull Requests 0 Wiki
Tree: 25b341ffc6
Branches Tags
MIVAS
/
data
/
log
/
1018.log

1018.log 2.5 KB
Histórico Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344 
  1. ==8327== 
    2. 

  2. ==8327== HEAP SUMMARY:
    3. 

  3. ==8327==     in use at exit: 552,546,716 bytes in 345,730 blocks
    4. 

  4. ==8327==   total heap usage: 1,073,700 allocs, 727,970 frees, 1,234,077,080 bytes allocated
    5. 

  5. ==8327== 
    6. 

  6. 

  7. 

  8. ==8327== 56 bytes in 1 blocks are definitely lost in loss record 1 of 22
    9. 

  9. ==8327==    at 0x484622C: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
    10. 

  10. ==8327== 
    11. 

  11. ==8327== 216 bytes in 14 blocks are possibly lost in loss record 2 of 22
    12. 

  12. ==8327==    at 0x4845B3C: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
    13. 

  13. ==8327== 
    14. 

  14. ==8327== 668 bytes in 111 blocks are possibly lost in loss record 4 of 22
    15. 

  15. ==8327==    at 0x4845BFC: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
    16. 

  16. ==8327== 
    17. 

  17. ==8327== 1,568 bytes in 4 blocks are possibly lost in loss record 7 of 22
    18. 

  18. ==8327==    at 0x4847D10: realloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
    19. 

  19. ==8327== 
    20. 

  20. ==8327== 3,902 (1,192 direct, 2,710 indirect) bytes in 1 blocks are definitely lost in loss record 9 of 22
    21. 

  21. ==8327==    at 0x131E0D94: g_type_create_instance (in /usr/lib/aarch64-linux-gnu/libgobject-2.0.so.0.5600.4)
    22. 

  22. ==8327== 
    23. 

  23. ==8327== 107,840 (30,141 direct, 77,699 indirect) bytes in 55 blocks are definitely lost in loss record 16 of 22
    24. 

  24. ==8327==    at 0x4845BFC: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
    25. 

  25. ==8327== 
    26. 

  26. ==8327== 603,772 bytes in 4,448 blocks are possibly lost in loss record 20 of 22
    27. 

  27. ==8327==    at 0x4847B0C: calloc (in /usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
    28. 

  28. ==8327== 
    29. 

  29. ==8327== LEAK SUMMARY:
    30. 

  30. ==8327==    definitely lost: 31,389 bytes in 57 blocks
    31. 

  31. ==8327==    indirectly lost: 80,409 bytes in 145 blocks
    32. 

  32. ==8327==      possibly lost: 606,224 bytes in 4,577 blocks
    33. 

  33. ==8327==    still reachable: 551,656,942 bytes in 340,060 blocks
    34. 

  34. ==8327==                       of which reachable via heuristic:
    35. 

  35. ==8327==                         stdstring          : 8,760 bytes in 151 blocks
    36. 

  36. ==8327==                         length64           : 3,368 bytes in 68 blocks
    37. 

  37. ==8327==                         newarray           : 1,936 bytes in 41 blocks
    38. 

  38. ==8327==         suppressed: 0 bytes in 0 blocks
    39. 

  39. ==8327== Reachable blocks (those to which a pointer was found) are not shown.
    40. 

  40. ==8327== To see them, rerun with: --leak-check=full --show-leak-kinds=all
    41. 

  41. ==8327== 
    42. 

  42. ==8327== For counts of detected and suppressed errors, rerun with: -v
    43. 

  43. ==8327== Use --track-origins=yes to see where uninitialised values come from
    44. 

  44. ==8327== ERROR SUMMARY: 871 errors from 26 contexts (suppressed: 0 from 0)
    45.