Sorry, no. That didn't fix it. It's still hanging around 31-32% CPU and 400mb of RAM. I'm running the latest Chrome on Win10 with a 4 core i7 CPU, a GeForce GTX 1060 video card, and 16gb RAM.
I'm not sure why it's running differently on your machine, but, speaking as a developer, it "working just fine on your computer" isn't a good metric. ;-)