I find Excel extremely buggy, almost to the point of unuseability. I am constantly restarting the program. Just to be able to do things like click a certain column or cell. I'm also getting "out of memory" errors when I try to save. Anyone else having similar issues?
Running on a Late 2011 Macbook Air.
I'm not having issues with Excel 2011 or 2016 on my Late 2013 rMBP, with the latter app is connected to a robust network connection.
I have, however, noticed a significantly different means of the two Excel applications (2011 & 2016, both connected to an Office 365 account) talking to MS's network which has negatively affected performance on one my my Macs (a 2012 Mac Mini Server that is transported to a field office and to my home office) that's not always connected to the internet; a test at the field office with the internet down brought Excel 2016 to its knees, but 2011 worked fine.
I'm using Little Snitch to check service and network connections.
Excel 2011 seems to run fine, and "talks" to my OneDrive and MS Office 365 through a service named "Microsoft Ship Asserts" (at least, that Service is running when I'm using MS Office 2011 apps), and both the OneDrive and Asserts Services get polled occasionally.
OTOH, Excel 2016 is talking to three network services very often: "nexus.officeapps.live.com", "login.live.com", and "osiprod-wus-bronze-000.cloudapp.net" - if I temporarily blocked any of those three services (with a Little Snitch Rule or manually), Excel 2016 choked, even on a simple document with no calculations being performed and with no restrictions to my OneDrive. I noticed that Excel 2016 activated those 3 network service connections immediately upon an Excel Window being clicked on (i.e., being clicked on from another application including the Finder), a calculation being made (via "Calculate Now"), or after several data entries - Excel 2016 seems to want to "talk" to those network services very often. When connected to a robust network connection Excel 2016 works for me without issue, given that MS's servers are likely still being hammered by us.
I'll be passing on my findings, rather, a gripe, to MS via their feedback panel.