Re: [I] Memory leak [age]

jrgemignani commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2296854488 @vladiksun There are some other memory leaks, for example #2046 which I am currently working on, that could be contributing factors. That particular one highlights quite a few other

Re: [I] Memory leak [age]

vladiksun commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2296684446 @jrgemignani I checked the fix. It works within one session. As I understand with more sessions there would be more memory consumption to keep the cache. For example using 100 connecti

Re: [I] Memory leak [age]

jrgemignani commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2278410068 @vladiksun This fix is now in all branches, except PG12 and PG11. Those are pending review and merge. If you want to test the latest for the branch you are using, try `dev_snapshot_`

Re: [I] Memory leak [age]

jrgemignani commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2278121782 @vladiksun It is in the master branch right now. I'll be making PRs for the other branches today. -- This is an automated message from the Apache Git Service. To respond to the mes

Re: [I] Memory leak [age]

vladiksun commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2277402122 @jrgemignani thanks for taking a look. We are waiting when it is ready then. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to G

Re: [I] Memory leak [age]

jrgemignani commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2276939020 @vladiksun PR #2028 Should address most of the issue with this memory leak. Although, there might be more, more subtle leaks. -- This is an automated message from the Apache Git Se

Re: [I] Memory leak [age]

jrgemignani commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2276609584 @vladiksun I do see the memory leak you are talking about and have narrowed it down to a few commands. -- This is an automated message from the Apache Git Service. To respond to th

Re: [I] Memory leak [age]

jrgemignani commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2276405294 @vladiksun I have not been able to reproduce a crash, but will keep trying. However, I am using the latest master branch and there have been fixes to the VLE caching mechanism since

Re: [I] Memory leak [age]

jrgemignani commented on issue #2020: URL: https://github.com/apache/age/issues/2020#issuecomment-2276185380 @vladiksun Yes, the VLE component does cache data for multiple contexts. It will only free them when the - 1. Transaction id changes (updates). 2. Maximum number of cached c

[I] Memory leak [age]

vladiksun opened a new issue, #2020: URL: https://github.com/apache/age/issues/2020 **Describe the bug** Potential memory leak **How are you accessing AGE (Command line, driver, etc.)?** - JDBC **What data setup do we need to do?** ```pgsql select ag_catalog.