> "ready" parser state only means that the parser has completed - that's not the end of the road though. Upon reaching that state change, several components (e.g. toolwindows) *begin* work. Inspections start running if they're configured to run automatically; toolwindows (code/todo/test explorers, code metrics, etc.) start querying, processing, and aggregating the parser state data. When inspections complete, the toolwindow refreshes, which can be another resource consumption peak.
3 minutes