Memory leak during transaction handling #557
Comments
novoj
added a commit
that referenced
this issue
May 10, 2024
According to heapdump - current way of switching catalog reference is not safe and there are references to old catalogs trapped in "catalogAccessor" lambda in entity collection. These changes aim to clarify the process of transitioning from one catalog version to another and avoiding the reference leak. According to heapdump - current way of switching catalog reference is not safe and there are references to old catalogs trapped in "catalogAccessor" lambda in entity collection. These changes aim to clarify the process of transitioning from one catalog version to another and avoiding the reference leak.
novoj
added a commit
that referenced
this issue
May 10, 2024
…tion-handling fix(#557): memory leak during transaction handling
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
evitaDB leaks memory when there are regular catalog updates in transactional mode. By studying heap dump we found that problem is inside
catalogAccessorlambda inEntityCollection. It seems there are situations where collections refer to the old catalog which in turn refers to old entity collections which in turn refer to yet older catalog instance and vice versa.Current way of reataching entity collections to new instances of the catalogs seems unreliable and we have to change it.
The text was updated successfully, but these errors were encountered: