603179 - After a hard reset, Firefox will no longer display windows.

Status: RESOLVED INACTIVE

(Firefox :: General, defect)

Description

[Mike Hoye]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-us) AppleWebKit/533.17.8 (KHTML, like Gecko) Version/5.0.1 Safari/533.17.8
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b6) Gecko/20100101 Firefox/4.0b6

After a hard-reset of my machine, Firefox will not display windows anymore. It will open, I can see the menu bar and interact with it, but new window and new tab simply don't display new windows. 

Running it from the command line, whenever I attempt to open a new window or tab I get the following error: 

2010-10-09 14:40:46.391 firefox-bin[589:613] Mozilla has caught an Obj-C exception [NSImageCacheException: Cannot lock focus on image <NSImage 0x1a106410 Size={0, 0} Reps=(
)>, because it is size zero.]

Restarting the Firefox in safe mode, with add-ons disabled, gets me in; on a hunch, I disabled the Feedback extension (ver. 1.0.3) and restarted the application, and now all appears to be well. I've since re-enabled it, and all continues to be well.

I don't claim to understand what's happened here, except that now it works again.

Reproducible: Always

Steps to Reproduce:
1. Hard-stop Firefox in just the right way at just the right time.
2. Restart Firefox
3. See nothing
Actual Results:  
No window, limited functionality.

Expected Results:  
The interwebs.

I'm not sure how to rank this - it seems like the most rare of corner cases, but it also cripples the product. Marking it "normal" and deferring to whoever triages it.

Comment 1

[Daniel Holbert [:dholbert]]

(Ran across this bug when searching for "Mozilla has caught an Obj-C exception" for an unrelated investigation)

I'm would expect (and am extremely hopeful that) this has become a non-issue in the 13 years that have passed since this was filed. Can't check at this point since unfortunately mhoye's bugzilla account is inactive, but I would be surprised we'd be getting more reports of this if it were still a thing.

(Also: the "Feedback extension" that mhoye mentions in comment 0 no longer seems to exist, at least as a disableable thing in about:addons, so to whatever extent that was involved, that part is maybe resolved?)

--> Closing as INACTIVE; if anyone can still repro (yikes), please reopen or file a new bug with up-to-date instructions/details. Thanks!