Release a libsql version that includes #2261 (local connection double close)

Open
#2,307 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 11 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Half a day
Newbie friendliness
15/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
c, go, rust, sqlite
Domain
databases, release

Research direction

This is a maintainer request to publish a new libsql tag that includes the fix from #2261, which is already merged; nothing in the payload asks for a code change. The release history is the place to look, starting from the latest tag libsql-0.9.30 and the merge of #2261. Done means a tag newer than 0.9.30 exists and contains the local Connection double-close fix. Contributors can help by testing a release candidate.

Written by the indexing model from the issue text.

Description

Hi! #2251 (local Connection closed twice on drop; sqlite3_close_v2 on a freed handle) was fixed by #2261 on 2026-10-13, thank you. The newest tag, libsql-0.9.30 (2026-03-19), predates the fix, so no release carries it yet.

Through go-libsql, the C binding's libsql_disconnect runs the drop on RT.spawn_blocking. In our CI that shows up as a random SIGSEGV on a tokio worker (sqlite3_close_v2 ← drop_in_place<libsql::local::connection::Connection> ← Arc::drop_slow ← tokio::runtime::task::raw::poll) in about 4–12% of test-binary runs on ubuntu-latest. Production services that close connections (pool retirement, shutdown) carry the same double free.

Could you cut a release (0.9.31 or later) that includes #2261? That would let go-libsql rebuild its static libraries (update-libsql.yml) and let us drop a fork that only cherry-picks this one fix. Happy to test a release candidate.

Dominant language
C
Stars
17.3k
Forks
562
Avg merge
10d 15h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tursodatabase/libsql

All issues in tursodatabase/libsql

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.