I am also starting to think this could be associated with the new update 3.0.11
Makes sense don't see a lot about it, forefox just updated recently to this version, and you have just noticed the error so it all kind of fits. Mozilla may have a hot patch soon about all i can think of....