This repository was archived by the owner on Aug 31, 2021. It is now read-only.
[[ Bug 22020 ]] Fix memory leak when dbsqlite connection fails #129
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch fixes a memory leak which occurs when opening a dbsqlite connection fails. As sqlite3_open will create a connection struct even if there is an error, sqlite3_close must be called regardless of the error returned when opening it.
Member
|
@livecode-vulcan review ok ccdac33 |
|
💙 review by @livecodeali ok ccdac33 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch fixes a memory leak which occurs when opening a dbsqlite
connection fails. As sqlite3_open will create a connection struct
even if there is an error, sqlite3_close must be called regardless of
the error returned when opening it.