Closed
Bug 720205
Opened 13 years ago
Closed 13 years ago
Tapping the tab close button doesn't remove the tab from the tab list immediately
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Tracking
(fennec11+)
RESOLVED
DUPLICATE
of bug 719494
| Tracking | Status | |
|---|---|---|
| fennec | 11+ | --- |
People
(Reporter: hsivonen, Assigned: blassey)
References
Details
Steps to reproduce on Galaxy Tab 10.1:
1) Go to http://arstechnica.com/
2) Open articles in new tabs until the system OOM reaper kills Nightly.
3) Reopen Nightly.
4) Open the tab switcher.
5) Tap the close X next to one or several tabs.
Actual results:
The tabs don't get removed from the tab list immediately when the Gecko thread is busy.
Expected results:
Expected the front end thread to remove the tab from the tab list immediately and take care of communication with Gecko ASAP but asynchronously.
Comment 1•13 years ago
|
||
I am hoping bug 719494 fixes this issue. We now close the tab right away, and let Gecko handle closing the actual <browser> asynchronously.
Comment 2•13 years ago
|
||
(In reply to Mark Finkle (:mfinkle) from comment #1)
> I am hoping bug 719494 fixes this issue. We now close the tab right away,
> and let Gecko handle closing the actual <browser> asynchronously.
Yeah, this sounds like a dupe of bug 719494. My first patch got backed out because it caused a crash, but I have a better one in the works.
| Assignee | ||
Updated•13 years ago
|
Assignee: nobody → blassey.bugs
tracking-fennec: --- → 11+
Priority: -- → P2
Comment 3•13 years ago
|
||
I think this is a dupe of bug 719494 (I'm gonna land that today), unless you're planning on trying to fix whatever is causing Gecko to be slow.
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 5•13 years ago
|
||
Brad, are you looking into the root problem of this Gecko slowness in another bug? If so, can you share the bug number?
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•