please log this in our issue tracker along with your test case, because it's not something I can fix in the near future.
My preliminary analyis is that there is no leak in our LOB management (unlike the first bug you reported). We just don't seem to be doing a very good job of compacting here, resulting in a file with tons of partially filled (1%) chunks. I would personally prefer to rework our LOB handling completely so we don't do any writes at all when reading from LOB's, but that would require that clients hold a transaction open when reading a LOB, which is not backwards compatible. -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
