==90024== Memcheck, a memory error detector
==90024== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==90024== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==90024== Command: /home/github/actions-runner/_work/Chaste/Chaste/Chaste/chaste-build-dir/lung/test/TestImpedancePostProcessor -malloc_debug -malloc_dump -memory_info
==90024== Parent PID: 68882
==90024== 
==90024== WARNING: pwritev(vector[...]) is an obsolete suppression line not supported in valgrind 3.15 or later.
==90024== You should replace [...] by a specific index such as [0] or [1] or [2] or similar
==90024== 
==90024== 
==90024== FILE DESCRIPTORS: 7 open (3 std) at exit.
==90024== Open file descriptor 115:
==90024==    <inherited from parent>
==90024== 
==90024== Open file descriptor 110:
==90024==    <inherited from parent>
==90024== 
==90024== Open file descriptor 4: /home/github/actions-runner/_work/Chaste/Chaste/Chaste/chaste-build-dir/memtest/TestImpedancePostProcessor_valgrind.txt
==90024==    <inherited from parent>
==90024== 
==90024== Open file descriptor 3: /home/github/actions-runner/_work/Chaste/Chaste/Chaste/chaste-build-dir/Testing/Temporary/LastTest.log.tmp
==90024==    <inherited from parent>
==90024== 
==90024== 
==90024== HEAP SUMMARY:
==90024==     in use at exit: 24 bytes in 2 blocks
==90024==   total heap usage: 5,600 allocs, 5,598 frees, 602,814 bytes allocated
==90024== 
==90024== LEAK SUMMARY:
==90024==    definitely lost: 0 bytes in 0 blocks
==90024==    indirectly lost: 0 bytes in 0 blocks
==90024==      possibly lost: 0 bytes in 0 blocks
==90024==    still reachable: 24 bytes in 2 blocks
==90024==         suppressed: 0 bytes in 0 blocks
==90024== Reachable blocks (those to which a pointer was found) are not shown.
==90024== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==90024== 
==90024== For lists of detected and suppressed errors, rerun with: -s
==90024== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)