If you add up
MEM% for all the identical looking chrome processes, then you have well over 100%, which is impossible. That's because those are not, in fact, separate processes, they're threads, which share the same memory space.
htop shows these by default, but see here for how to change that and get a view that will make more sense to you.
Your total used RAM is 1047 of 1727 MB, so you do not have memory problems. When looking at memory stats, keep in mind that virtual memory, more properly: virtual address space, shown here as
VIRT is not real memory. It's address space, and most of the addresses aren't used and don't correspond to anything. On linux, the size of this pretend space can be up to 4 GB per process, even if you don't have that much available to start with.
A decent metric of the amount of RAM actually consumed is the RSS or resident memory size (in
RES). If you eliminate threads from the view, you'll see there's actually only one 142 MB
google-chrome process (actually there may be a handful of genuinely separate chrome processes, but not dozens). Another significant stat if you are trying to diagnose system performance problems is the amount of CPU time consumed (
TIME+), but again nothing looks particularly out of line here WRT chrome.