You probably don’t want to read this. But it’s here, on the off-chance that I forget how to fix it and some day stumble across the solution on my own blog.
I use Excel all day, every day, 24/7, because that is how businesses run.
Anyway, when I work from home it is real crashy. I thought it had to do with VPNs, but after reading the Internet and trying things, I discovered IT WAS NOT related to VPNs. It was related to monitors, or rather, the lack of my external monitor (please note this was not discovered in error logs, just by a lucky guess).
When I opened up the VBA editor on just my MacBook, the VBA editor would have a bunch of title bars and things off-screen. At work I have the VBA editor on my external monitor, and Excel itself on my MBP display. When the VBA editor went from big-ass monitor to not big-ass laptop display, it got funky with placement of title bars and windows and such.
Once in the VBA editor, I’d try to move things, or just try to deal with it and start writing things. After a few minutes, it would always crash with this error report:
Microsoft Error Reporting log version: 2.0
Date/Time: 2013-12-06 16:41:17 +0000
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 22.214.171.124030
Crashed Module Name: libobjc.A.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x00006d4b
Blame Module Name: MicrosoftComponentPlugin
Blame Module Version: 126.96.36.199030
Blame Module Offset: 0x00045370
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Crashed thread: 0
SO. After some Googling and I had a feeling that it may have had to do with VBA being sad about the screen real estate. No one had this exact problem, but similar problems with Word.
I opened Excel, opened the VBA editor, and then quickly changed my screen resolution, which forced all VBA editor elements to actually be on-screen, instead of off in the ether.
AND THAT FIXED IT.
HOORAY NO ONE CARES!