Memory Leak Seen with ttisql Via Valgrind Tool
(Doc ID 2463542.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle TimesTen In-Memory Database - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Memory leak seen with ttisql via valgrind tool
==599== Memcheck, a memory error detector
==599== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==599== Command: /u01/timesten/TimesTen/tt1122/bin/ttIsqlCmd DSN=XXXXXXXXX
=16068== LEAK SUMMARY:
==16068== definitely lost: 380 bytes in 2 blocks
==16068== indirectly lost: 0 bytes in 0 blocks
==16068== possibly lost: 272 bytes in 1 blocks
==16068== still reachable: 138,462 bytes in 34 blocks
==16068== suppressed: 0 bytes in 0 blocks
==16068== Reachable blocks (those to which a pointer was found) are not
==16068== To see them, rerun with: --leak-check=full --show-reachable=yes
==16068== For counts of detected and suppressed errors, rerun with: -v
==16068== ERROR SUMMARY: 9106 errors from 300 contexts (suppressed: 13 from
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document