Re: Chrome Memory Issue
MS just keeps shooting themselves in the foot when it comes to IE. In theory, IE is our std browser in our global company because we are Windows/Active Directory based. We also implemented WSS 3.0 (free Sharepoint 2007) many years ago, which would not run in any other browsers like Chrome. Heck, it needed Quirks mode just to run in IE.
So I upgraded my local biz unit Sharepoint to 2013 foundation last summer, expecting to get rid of Quirks mode and let it work in other browsers. That worked while using IE8 or IE9, and it did work in Chrome. But then IE11 showed up, pushed by end of support for 8.9 and 10. It sucks with SP 2013. SP 2013 doesn't support Edge, tries to force IE10 emulation with X-UA meta tag. But that doesn't even work, unless you put site in Compat View Settings, many things just do not work. I've been looking for tech reasons for that and have basically struck out, it's just gotten too complicated what the rules are in that world of browser detection.
So Sharepoint, one of MS prizes, has it's current version work better with Chrome. Ridiculous. And I'm not seeing where upcoming SP 2016 makes this any better. All they did was focus on "cloud hybrid" ability instead of core usability in their own browser!
Another great IE/Chrome story: I wrote an Extjs (HTML5) dashboard app which runs from browser on thin clients on shopfloor. It makes server calls every 30 seconds to get PLC data saying if machine up/down and how fast it is running versus target speed. So I deployed Win 7 embedded bricks, which of course ran IE, and mounted monitors by the machines for supervisors to review when they came by.
It didn't work, had to install and run app in Chrome. Seems IE detected my application as an "endless loop" and just shut it down after a couple of hours, nothing I could do about it. Nice work MS.