QLever Waiting for response crawl or Cancel spinner causing browsers to consume CPU and memory

[pfps]

Running a complex query in QLever on my Linux machine causes both Firefox and Chromium to consume 100% of a thread and to use more and more memory. The memory consumption is faster in Firefox but even Chromium increases memory consumption by about 1% of 8GB every other minute or so.

I don't know whether this is because of bugs in Firefox and Chromium or because the script is actually consuming memory.

[joka921]

Thanks for reporting this. Can you please share the query + the dataset, and tell us, what you did exactly?
I assume that you clicked on "execute" in the UI, or did you do anything else (like click on Analyze or click on "show all results" after the first results were shown etc.

[pfps]

The behavior happened on long-running queries like https://qlever.cs.uni-freiburg.de/wikidata/QUYHNB. But I don't think that it had any relationship to the query, as no results were returned. All I did was click on Execute - no analysis or asking for more results or anything.

The problem is not occurring now. I don't know what has changed. I did update my system in the meantime, including Firefox.