Skip to content
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

Bug: Kuzu hangs with undirected recursive join and TRAIL path semantic #4540

Open
sapalli2989 opened this issue Nov 17, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@sapalli2989
Copy link
Contributor

Kùzu version

v0.7.0

What operating system are you using?

Debian 12

What happened?

Setup:

CREATE NODE TABLE V (id INT64, PRIMARY KEY(id));
CREATE REL TABLE links_to (FROM V TO V);
CREATE (v1:V {id: 1})-[:links_to]->(v2:V {id: 2})-[:links_to]->(v3:V {id: 3}),
(v4:V {id: 4})-[:links_to]->(v2),(v4)-[:links_to]->(v5:V {id: 5}), (v6:V {id: 6})-[:links_to]->(v1),
(v8:V {id: 8})-[:links_to]->(v9: V{id: 9}),
(v10:V {id:10});

Next query will start, but timeout after couple of seconds due to default WALK semantic:

kuzu> MATCH (:V {id: 1})-[:links_to*]-(v2:V) RETURN DISTINCT v2.id;
Error: Buffer manager exception: Unable to allocate memory! The buffer pool is full and no memory could be freed!

Using TRAIL will hang CLI, possibly creating an infinite loop (high CPU load, no segfault error caught):

kuzu> MATCH (:V {id: 1})-[:links_to*TRAIL]-(v2:V) RETURN DISTINCT v2.id;
Pipelines Finished: 2/5
Current Pipeline Progress: 0%

Expected result: [2,3,4,5,6]

Related: #4072

Are there known steps to reproduce?

No response

@sapalli2989 sapalli2989 added the bug Something isn't working label Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant