PoB high CPU in some tabs and when typing

Check version

• I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

• I've checked for duplicate issues by using the search function of the issue tracker

How is Path of Building expected to behave?

Expected to not lag when typing or not have such high CPU usage

How does Path of Building behave?

Whenever I type something in the Custom Config box, labeling Skills set names, typing to search a skill or support in the Skill tab (and maybe some other places I haven't found yet) typing will slow down and CPU usage goes way up. Clicking to select a support gem for a skill, for example, can take anything from 2 to 5+ seconds.

Seems to be related to the amount of information stored in the build. A fresh empty build has no issues, but when you add support gems, auras, gear and configurations, these typing areas slow down to a crawl. I tested by copying by hand my own build into PoB, creating items from withing the application instead of importing my character so it has no chance of it being some import bug and it still slows down.

How to reproduce the issue

1. Import or fill up a build as normal, add skills, support gems, auras, and gear
2. Select an area that can be typed on such as Skill Tab labels or Custom Config (other zones like Passive Tree menu, Gear menu, crafting menu and similar don't have any issues when typing)
3. CPU usage goes up by a lot slowing down the application while typing and simply having some areas open at the same screen

Character build code

Simulated my character into PoB

https://pobb.in/BdGwMWLa0QTx

Screenshots

Screen Focused on Share/Import Tab:

Screen Focused on Items Tab:

Screen Focused on Skills Tab:

Screen Focused on Tree Tab:

Screen Focused on Notes Tab:

Screen Focused on Calcs Tab:

Screen Focused on Configs Tab:

Typing in the Configs Tab:

Reproduce the slowdown with the linked pobb.in build by typing in the Custom Config box, Skill tab search, or skill labels while profiling CPU usage. Compare a populated build with an empty build and identify the work triggered by typing or by keeping these areas open. Done means typing and selecting support gems no longer take 2–5+ seconds and CPU usage is substantially reduced.