I need to work with a very huge page (there are a lot of elements, really) with selenium and Chromedriver. After navigation happened and page loaded test gets hung for more than 2 hours. Chrome is consuming 100 % CPU during this process. I suspect it to parse the loaded page. 
Is there a way to avoid or handle it somehow? (I know that the page should not be that huge, but it is a different story)
Thanks in advance for your help.
All, thanks for your help. I found the root cause. Actually the problem was with non optimal usage of find_elements. 
Even when it is called once it executes for ages. Replaced with a workaround using find_element and it started to work. The workaround is fragile, but it's better than nothing.
Chromedriver works with page for too long