[GH-ISSUE #278] Deadlock when database has more than 100 top-level collections #204

New issue

Open

opened 2026-10-02 22:10:50 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-10-02 22:10:50 -06:00

Owner

Originally created by @Teejirapat on GitHub (Sep 24, 2026).
Original GitHub issue: https://github.com/appy-one/acebase/issues/278

I found a deadlock issue when the database has more than 100 top-level collections/nodes.

When the root node grows beyond 100 children, AceBase switches the root to a B+tree. After that, writing to an existing top-level collection can hang indefinitely.

Suspected cause

It looks like the B+tree code in NodeReader.getChildStream() creates root child paths with a leading /:

${this.address.path}/${key}

When the root path is empty, this produces:

/collection_1

while the expected path is:

collection_1

Originally created by @Teejirapat on GitHub (Sep 24, 2026). Original GitHub issue: https://github.com/appy-one/acebase/issues/278 I found a deadlock issue when the database has more than 100 top-level collections/nodes. When the root node grows beyond 100 children, AceBase switches the root to a B+tree. After that, writing to an existing top-level collection can hang indefinitely. ### Suspected cause It looks like the B+tree code in `NodeReader.getChildStream()` creates root child paths with a leading `/`: `${this.address.path}/${key}` When the root path is empty, this produces: `/collection_1` while the expected path is: `collection_1`

gitea-mirror referenced this issue

2026-10-02 22:11:15 -06:00

[PR #204] [MERGED] Bump json5 from 2.2.1 to 2.2.3 #164