My apologies for the relatively light link salad today, as well as the lack of any more substantial post. Chemo brain seems to have infected my MacBook Pro, and I’ve spent most of my blogging time this morning dealing with rebooting to clear a virtual memory issue that seems to be able to persist even through a shut down cycle.
I’ve actually been wrestling with this for a while. It’s a subtle error, and only appears on occasion, so my trip to the Genius Bar a while back was pretty much a waste. But when the error does appear, TextPad stops being able to save, which screws up my blog post build. Restarting TextPad doesn’t help at that point. If I don’t reboot then, eventually I get a system error that the startup disk is out of space for virtual memory. Mind you, this is a disk with 100GB available. At that point, there’s nothing for it but to Force Quit any open applications and reboot. And the Mac’s attempt to save my working state means that sometimes I come back from the reboot with the error still in play. Which requires yet another reboot.
So far, attempted fixes include replacing the hard drive in case of a bad sector, upgrading to Lion in case of an oddball system incompatibility in the previous OS release, and swapping Web browsers, twice. The problem still comes back, on an apparently random basis. This morning’s outbreak was by far the worst yet.
Of course, here’s me in late stage chemo, when I am not at my troubleshooting best. It’s entirely possible this is some obscure form of user error. But I can’t replicate it, and because I can’t replicate it, I can’t even do the requisite troubleshooting to pin down the offending application(s) or Web sites. Meanwhile, I’ve been considering buying a MacBook Air, and I’m now wondering if going to all new hardware will allow me to simply walk away from the issue.
All of which is a very long-winded way of apologizing for the dearth of new content today. I lose enough quality blogging days to chemo brain. It’s frustrating to lose one to tech wonkery.