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

query causing QLever to crash #1606

Open
pfps opened this issue Nov 6, 2024 · 4 comments
Open

query causing QLever to crash #1606

pfps opened this issue Nov 6, 2024 · 4 comments

Comments

@pfps
Copy link

pfps commented Nov 6, 2024

This query appears to cause the QLever Wikidata service to crash:

SELECT DISTINCT ?first ?firstLabel WHERE {
{ SELECT DISTINCT ?c WHERE {
?c wdt:P31/wdt:P279*/wdt:P31/wdt:P279*/wdt:P31 wd:Q24017465 .
} }
?first wdt:P279* ?c .
OPTIONAL { ?first rdfs:label ?firstLabel . FILTER ( lang(?firstLabel) = 'en' ) }
}

On my local QLever server evaluating the query causes unbounded memory usage.

I think that this query used to work a few months ago.

@pfps
Copy link
Author

pfps commented Nov 6, 2024

SELECT DISTINCT ?first ?firstLabel WHERE {
?c wdt:P31/wdt:P279*/wdt:P31/wdt:P279*/wdt:P31 wd:Q24017465 .
?first wdt:P279* ?c .
OPTIONAL { ?first rdfs:label ?firstLabel . FILTER ( lang(?firstLabel) = 'en' ) }
}

may cause the same problem.

@pfps
Copy link
Author

pfps commented Nov 6, 2024

I'm also seeing queries that do not cause a memory panic but have a resident memory footprint of 180GB on a 196GB machine when the max memory size is set at 96GB and the max cache size is set at 32GB. Is this expected?

@hannahbast
Copy link
Member

@pfps Thanks for pointing this out to us and for the reminder. That is indeed a recent regression and should not happen. We will investigate asap.

Notifying @RobinTF and @joka921

@hannahbast
Copy link
Member

We have identified #1595 as the cause of the problem. If it's reverted (which I now did for https://qlever.cs.uni-freiburg.de/wikidata), a query likes https://qlever.cs.uni-freiburg.de/wikidata/Gs948g runs through without problems (even with a rather small amount of RAM).

We will investigate further

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants