+
Skip to content

fix: explicitly close the database on account removal #5814

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

Merged
merged 1 commit into from
Jul 30, 2024
Merged

Conversation

link2xt
Copy link
Collaborator

@link2xt link2xt commented Jul 29, 2024

Closes #5809

@link2xt link2xt requested a review from iequidoo July 29, 2024 23:13
@link2xt
Copy link
Collaborator Author

link2xt commented Jul 29, 2024

I have tested in #5811, this actually fixed the problem. CI passed on Windows without try_many_times.

@link2xt link2xt merged commit 0fceb27 into main Jul 30, 2024
37 checks passed
@link2xt link2xt deleted the link2xt/close-db branch July 30, 2024 00:22
WofWca added a commit that referenced this pull request Apr 17, 2025
If 5 times is not enough, 60 will probably not be enough either.

This is mainly an attempt of improving the situation with
deltachat/deltachat-desktop#3959.

The `remove_account` RPC call would make the RPC server
stop responding to all other requests,
which is basically equivalent to a one minute hang.

Additionally, `try_many_times` appears to be unnecessary after
#5814 (comment).
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 this pull request may close these issues.

Database not closed immediately on account removal
2 participants
点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载