We were seeing out-of-memory errors when launching on Chrome version 58 on Windows (both 32-bit and 64-bit). After some investigation, the root cause appears to be a regression introduced in Chrome 58. We are currently working with Google to investigate this issue and expect a Chrome update to resolve this. When an update or other work-around is available, the details will be noted here and this ticket closed.
Update 5/29: Google have submitted a fix to this issue, and fix is in today's Chrome Canary build, version 60.0.3109.0. We expect the fix to appear in a Chrome general release version soon.
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-44727 in the post.