July 6, 2009 3 Comments
A few weeks ago, I noticed a behavior that I had frankly not seen before – my Firefox browser started to crash. Firefox has always been stable in my experience (note: using a Dell laptop) and I found this to be perplexing.
I noticed that it happened just after I clicked links in Twitter, and furthermore, after some days of observation, it became evident that the crashing only happened in conjunction with links from one site – Mashable.com.
Now I’d never had problems with the Mashable site before, and always enjoyed the updates from there. But I began to have a nervous tic when I’d see Pete Cashmore’s avatar in my tweetstream.
I put out several tweets over the course of a couple weeks about this problem, wondering if the Mashable folks had perhaps added some widget or other such on their site that would cause this. I had not added-on any new Firefox extensions in recent weeks. Then the issue seemed to resolve itself after upgrading to Firefox 3.5. Nice. Case closed. Except for one thing…
To my surprise, I heard from Mashable’s CTO (through LinkedIn for some reason) asking for whatever information I could give to help figure out “what wasn’t playing nice.” Now I don’t know anybody at Mashable, and I’m not a particularly important person, but I was quite impressed that Frederick reached out directly and tried to help. Since the upgrade seemed to resolve it, I’m not sure I can troubleshoot any further, but I’ll put a big check mark in the Win column for these folks, for “listening” and following up. And, I’m glad to have no more nervous tics about clicking on interesting Mashable links!