Skip to content

Cleanup batches inside the engine if they were not released explicitly before disconnection#8341

Merged
dyemanov merged 1 commit intomasterfrom
batch-cleanup
Dec 5, 2024
Merged

Cleanup batches inside the engine if they were not released explicitly before disconnection#8341
dyemanov merged 1 commit intomasterfrom
batch-cleanup

Conversation

@dyemanov
Copy link
Copy Markdown
Member

@dyemanov dyemanov commented Dec 4, 2024

This avoids a resource leak (it's mostly about TempSpace). Easy to reproduce - just open a batch, push a significant number of records through the batch and disconnect. You'll get an assertion fb_assert(m_tempCacheUsage == 0); inside ~GlobalObjectHolder() and may also notice temporary files still existing.

Init/cleanup logic of JBatch is changed to match JResultSet and JReplicator.

…y before disconnection. This avoids a resource leak (it's mostly about TempSpace).
@dyemanov
Copy link
Copy Markdown
Member Author

dyemanov commented Dec 5, 2024

It it worth backporting into v4/v5?

@dyemanov dyemanov deleted the batch-cleanup branch December 10, 2024 08:58
dyemanov added a commit that referenced this pull request Dec 10, 2024
…y before disconnection. This avoids a resource leak (it's mostly about TempSpace). (#8341)
@mrotteveel mrotteveel changed the title Cleanup batches inside the engine if they were not released explicity before disconnection Cleanup batches inside the engine if they were not released explicitly before disconnection Jul 11, 2025
@mrotteveel mrotteveel added the rlsnotes60: no Intentionally not added to the Firebird 6.0 release notes. label Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants