Chrome renders each page (tab) in a different process. This makes it faster on multi-processor machines.
The behaviour you're seeing is normal.
futex_wait_queue_me
refers to a type of mutex lock (fast userspace mutual exclusion) that is used to schedule many processes work on one processor. The state indicates that your process is enqueued to receive the lock.
Sometimes, an unusually high amount of waiting for a lock can be caused by cpu throttling, but most often, it's normal. Take a look at the sort of website you have open; Perhaps something like Flash is causing the high CPU load.
To see what tabs or plugins are slowing down your system or filling up your memory, you can use Chrome's built in task manager:
In my example, omgubuntu's javascript uses a lot of cpu.
/proc/$pid/smaps
and see if Pss is lower than Rss.If so, it's shared.