Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sqlCache retains data (and other properties), possible memory leak #2027

Open
paulrutter opened this issue Jan 8, 2025 · 1 comment · May be fixed by #2028
Open

sqlCache retains data (and other properties), possible memory leak #2027

paulrutter opened this issue Jan 8, 2025 · 1 comment · May be fixed by #2028

Comments

@paulrutter
Copy link
Contributor

We recently observed an out of memory situation with AlaSQL 4.6.0.
It seems like the sqlCache (which is enabled by default), retains more information than it should.

See the attached screenshot of the heapdump, where it shows the sqlCache retaining properties like data, but also other information.

I doubt that this information should be stored in the cache, as it makes the cache much larger than required.
As a workaround i can either disable the cache, or reduce the MAXSQLCACHESIZE, but i'm not sure of the performance implications of doing this.

It seems like the objects stored in the cache should be stripped of any query execution specific information.

image
image

@mathiasrw what do you think?

paulrutter added a commit to blueconic/alasql that referenced this issue Jan 8, 2025
…mory leak AlaSQL#2027

- Remove the `data` property from the sql cache after executing the query
@paulrutter
Copy link
Contributor Author

See #2028.

paulrutter added a commit to blueconic/alasql that referenced this issue Jan 8, 2025
paulrutter added a commit to blueconic/alasql that referenced this issue Jan 9, 2025
paulrutter added a commit to blueconic/alasql that referenced this issue Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant