And to confirm that problem is still there, please run it against at least latest released version (2.1.214), or even better against current git build. I have that feeling that you just run queries with LOB in the result which causes extensive LOB cloning. Try to add ;LOB_TIMEOUT=1000 (1 sec instead of default 5 min) . On Monday, May 22, 2023 at 2:45:23 AM UTC-4 Andreas Reichel wrote:
> Greetings! > > On Sun, 2023-05-21 at 23:42 -0700, Arjun Sahoo wrote: > > Reproducing the test case is easy, keep on ingesting and deleting records, > you will see the memory usage increasing over time. If if query the table > simultaneously , you will reach the trend faster. > > > > You will need to write a self containing unit test simulating this, Only > this way people will help ypu. > > Best regards > Andreas > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/84e85db2-fc01-4e92-a4d2-6e162ec3a30bn%40googlegroups.com.
