After refactoring some Entity Framework Core queries, my application stopped responding. I traced the issue to `sqlite3.dll`, which executes a generates SQL statement that - apparently - does not return. I have copied the query and created a small DB that shows the issue. The database file can be downloaded [from here](https://budgetmagicwand-sto.energycdn.com/dl/UgWid3ofPxwEWk25-ZcpQw/1621372871/846603926/609af5478c6980.74164842/Problem.db). The statement generated by EF Core is rather large, [so I put it in a pastebin](https://pastebin.com/v0hDN3NY). When I try to execute the statement in the sqlite browser, htop states it writes a lot to disk, then runs out of memory after a minute or so. Is this my fault for forcing EF Core to generate a too complex query or is this a real problem?