-
Notifications
You must be signed in to change notification settings - Fork 52
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
Comments
SELECT DISTINCT ?first ?firstLabel WHERE { may cause the same problem. |
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? |
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 |
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.
The text was updated successfully, but these errors were encountered: