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

std::bad_alloc on simple broken query #46

Closed
niklas88 opened this issue Apr 11, 2018 · 1 comment
Closed

std::bad_alloc on simple broken query #46

niklas88 opened this issue Apr 11, 2018 · 1 comment

Comments

@niklas88
Copy link
Member

I'm trying to recreate the mediator-facts list used by Aqqu on the final freebase. Sadly my attempts provoked some QLever crashing. Before it crashes it uses a lot more RAM but it doesn't look like it quite hits out of memory. Especially since that should go to swap or awake the mighty OOM Killer.

In this query the order is wrong and thus ?s and ?o have the same function, it is NOT the correct mediator-facts query

PREFIX fb: <http://rdf.freebase.com/ns/>
SELECT DISTINCT ?s ?left ?right ?o WHERE {
    ?cvt fb:freebase.type_hints.mediator "true" .
    ?s ?left ?cvt .
    ?o ?right ?cvt .
}
LIMIT 100
@niklas88
Copy link
Member Author

niklas88 commented Aug 2, 2018

I've now collected a QLever log for this
qlever_crash_bad_alloc_broken_query.txt
also I now think QLever in fact just runs out of memory. The swap was was completely full and we've already seen a few OOM situations result in std::bad_alloc

@niklas88 niklas88 closed this as completed Aug 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant