I cannot address issues with Chrome other than that I wasn't particularly impressed with it. Matter of personal tastes, no doubt.
However, I can tell you that with only 2 GB of RAM, Windows doesn't like you very much. The problem is, of course, that Windows has become a virtual demand-paging system (ever since WinNT came around). There is a common factor for ALL (repeat and emphasize ALL) virtual demand systems - low memory just KILLS their performance. Flat out KILLS them. It was true for WinNT and is still true for Win10. Heck, my OpenVMS machine for the Navy didn't like low-memory situations and they damned near invented the virtual, demand-page, least-recently-used retirment system in the 1970s.
There is an old adage related to virtual, demand-page systems:
When the system swaps, the world stops. This is true because the memory management software is seen as higher priority than almost any other software you might have.
Usually, when the swap/page manager is running, it outranks every other piece of software you've got unless you have some home-grown real-time code that is non-swappable. Device drivers have these attributes. Certain laboratory experiment packages do this. Most user code does not.
Further, if you boost the priority of your code over the swap code, it won't help if you need to swap - because you will trigger a page fault, enter an involuntary wait state, and wait for memory management anyway. I can't tell you what to do, but I can remotely diagnose that if you only have 2 GB of RAM, you are probably going to continually face issues with low memory leading to paging delays.
Just for snorts and giggles, if you weren't up on paging, here is a reference article that is a decent overview.
https://en.wikipedia.org/wiki/Paging