Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

[6.x.x] Fix a memory leak in the XPath 3.1 Arrow Operator implementation#175

Open
adamretter wants to merge 4 commits intodevelop-6.x.xfrom
6.x.x/hotfix/arrow-operator-memory-leak
Open

[6.x.x] Fix a memory leak in the XPath 3.1 Arrow Operator implementation#175
adamretter wants to merge 4 commits intodevelop-6.x.xfrom
6.x.x/hotfix/arrow-operator-memory-leak

Conversation

@adamretter
Copy link
Member

Backport of #174

The Arrow Operator implementation previously did not free the reference to the Context Sequence on its left-side. This meant that it would be kept in-memory if the compiled query was sent to the XQuery Pool for reuse. This PR fixes that issue so that the memory is correctly freed when the query completes execution. Additionally there was also a possible resource leak if a Function Reference provided to the Arrow Operator was not of the expected cardinality, that is now fixed as well.

@adamretter adamretter added this to the elemental-6.9.1 milestone Mar 9, 2026
@adamretter adamretter self-assigned this Mar 9, 2026
@adamretter adamretter added the bug Something isn't working label Mar 9, 2026
@cla-bot cla-bot bot added the cla-signed label Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working cla-signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant