Fix deadlock when connecting after opening database #170
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
stevensJourney
approved these changes
Apr 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PowerSyncDatabaseImpl.connectused to callwaitReady()inside ofmutex.withLock. That's unfortunate, becauseinitializealso acquires the mutex inupdateSchemaInternal. So, when callingconnect()immediately after creating a database, there's a potential for a deadlock. The mutex must only be acquired after waiting for the database to be initialized.To validate the fix, I've migrated the sync tests to stop calling
connectInternaland instead use the publicconnectmethod. This requires customizing the HTTP client engine passed to the sync engine, for which I've created an (internal) method next to thePowerSyncDatabasefactory method.Closes #169.