The pictures are not very useful, because they don't tell use who is holding onto the data. There is no leak in ValueTimestamp itself, the leak is probably because something somewhere is keeping a reference on some part of H2's object graph. Since this is working fine for us, your only real option is to fire up a heap analysis tool like the Netbeans memory profiler and track down the places that are unnecessarily holding onto references into H2.
-- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
