This repository was archived by the owner on Jul 30, 2020. It is now read-only.
querydb process pegs CPU #82
Comments
|
Is it still reproducible? Or just an instance of #43 (comment) ? |
|
I'm betting that #43 will solve this, but I'll nuke the cache files for some of my larger projects and keep an eye out for a repro tomorrow. |
|
Has this been resolved? |
|
Sorry, busy week at work. Haven’t been able to reproduce, I think the added serialization fixed did the trick. Thanks for the fix! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've got two
querydbprocesses on my system stuck in what looks like a tight loop calling xstat. Unfortunately I don't have debug symbols for the binary, but I profiled it and dumped the flamegraph, which should give some idea of where cquery's spending its time.querydb-flamegraph.svg.zip
The text was updated successfully, but these errors were encountered: