289309 - Ctrl+N doesn't open new window

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Kevin Pratt]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 (ax)

Hitting Ctrl+N should open a new window, but it does not open the window.  It
does however allocate more memory for it. Looking at task manager, firefox has
15,588 K allocated, ctrl+n causes this to increment to 16,260, 16,808 17,232,
18,088, and so on... (it looks consistent up through at least 44M).  Minimizing
firefox drops this down to 1,540K.  Then maximizing again put this number to
~9M.  This cycle was repeatable.

Then, I attempted to close the browser, and the mem usage jumped from ~10M up to
43,396K and the program remained in the process list.  I attempted to open
firefox back up, but that failed (a second ff instance appeared in the process
list, but dissappeared a second or two later).

So I killed the ff process, and restarted it, and it is still exhibiting all of
the above described behavior.

And I've just restarted the machine, but it still exhibits the same behaviour.

Reproducible: Always

Steps to Reproduce:
1. Open Firefox
2. Do Ctrl+N or File->New Window
3. Watch it not open a new window.

(as for how it got into this state.....I don't know)
Actual Results:  
the program allocates more memory, but does not open a new window

Expected Results:  
Allocate the requisite memory, and then open a new window

I have All-in-One Gestures 0.12.4 (in case there are any known breakage issues
related to that) installed, and originally noticed the problem when it wasn't
responding to mouse gestures correctly (the bottom status bar displays the
correct mouse gesture and intended result (as it usually does) but nothing happens. 

And as a side-note, this is a machine at work, so I will need to get firefox
working again somewhat soon, but if there is further debug information I can
provide in the next couple days please let me know how and what I need to do.

Comment 1

[Gabriel Chadwick]

This works for me using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8b2) Gecko/20050406 Firefox/1.0+

I you get more information on how to reproduce the bug please reopen. Try
creating a new profile to see if it solves the problem.

Comment 2

[Kevin Pratt]

Update:  Creating a new profile did in fact fix this for me.