Closed
Bug 856072
Opened 12 years ago
Closed 12 years ago
Defect - Browser gets stuck after closing/opening multiple tabs
Categories
(Firefox for Metro Graveyard :: Browser, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: virgil.dicu, Unassigned)
References
Details
(Whiteboard: feature=defect c=tbd u=tbd p=tbd)
Mozilla/5.0 (Windows NT 6.2; rv:22.0) Gecko/20130329 Firefox/22.0
I'm seeing this a bit too often lately. The browser gets stuck after several operations. I can access Windows' menus: charm bar, or can change Firefox settings (show tabs), but can't close/open new tabs or type in page or URL bar.
This is probably always related to closing and opening tabs.
I can reliably reproduce with the following steps:
1. Activate "Always show tabs" from Settings.
2. Open five-six tabs using the + button.
3. Close each tab using the x button.
4. Repeat steps 2,3 while clicking faster through tabs if it can't be reproduced at first
Actual result: can't close/open new tabs or type in page or URL bar. restart needed to resume.
Can't find a good story to block against, so filing separately.
Updated•12 years ago
|
Blocks: metrov1it6
Priority: -- → P1
Summary: Browser gets stuck after closing/opening multiple tabs → Defect - Browser gets stuck after closing/opening multiple tabs
Whiteboard: feature=defect c=tbd u=tbd p=tbd
Comment 1•12 years ago
|
||
I think this could have been caused by the same issue as Bug 856244. If you double click the add new tab button fast enough, you can end up with your clicks trapped.
Updated•12 years ago
|
Updated•12 years ago
|
Updated•12 years ago
|
Priority: P1 → --
Comment 2•12 years ago
|
||
p=3
Reporter | ||
Comment 4•12 years ago
|
||
I can no longer reproduce this with the latest build - haven't had any such problems while testing yesterday. Not sure what fixed this, so resolving as WFM. Probably bug 856244 should have been fixed as well.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•12 years ago
|
No longer blocks: metrov1defect&change
You need to log in
before you can comment on or make changes to this bug.
Description
•