Whelp, it's got to be me, my Firefox install, and Mac OS X. Terminal reveals:
Fri Feb 27 16:58:30 Macintosh.local firefox-bin[67035] <Warning>: CGSResolveShmemReference : reference offset (65264) exceeds bounds (32768) on shmem obj 0xc789 2009-02-27 16:58:30.521 firefox-bin[67035:10b] Mozilla has caught an Obj-C exception [NSInternalInconsistencyException: Error (1000) creating CGSWindow] And to eliminate any (of my own) doubt in Ubiquity, I've tried a clean profile which crashed the first couple times I tried to start Firefox with it, then was fine, installed latest Ubiquity and it was still fine. Switched back to default profile and uninstalled Ubiquity, re- installed and Ubiquity was fine. Occasional crashes on my default profile still prompted me to disable all add-ons and crashes still occur, but not predictably. Usually very soon after Firefox starts if at all. I have NO idea why my problems started with finding the update for Ubiquity and trying to apply it, and why at first crashes occurred extremely reliably with Ubiquity enabled and not at all when disabled, but I figure it's safe to say that it was coincidence or corrupted data, Firefox and Mac OS UI framework weirdness and not Ubiquity. Thanks for the tips - I'll be more diligent before posting in the future. I'm going to reinstall Firefox - hope I don't have to eradicate it from my system and start over to get my favorite browser back to stability. Cheers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
