Closed
Bug 1303322
Opened 8 years ago
Closed 7 years ago
Firefox will crash when closing a tab from top tabs and rapidly tapping "+"
Categories
(Firefox for iOS :: General, defect, P1)
Tracking
()
VERIFIED
FIXED
Iteration:
1.16
People
(Reporter: SimonB, Assigned: farhan)
References
Details
(Keywords: crash, reproducible, Whiteboard: [MobileCore])
Attachments
(1 file)
|
65.35 KB,
text/plain
|
Details |
Build: 0295d92db2 Device: iPad Pro iOS: 9.3.5 Steps to reproduce: 1. Open Nightly and tap on the New tab "+" button 2. While tapping on the "+" button, rapidly tap the "x" button on a tab to close it Actual results: - Firefox will crash See video for more information: https://www.youtube.com/watch?v=6VjBDmgD_rc
|
||
Updated•8 years ago
|
Rank: 2
Priority: -- → P3
Whiteboard: [MobileAS]
|
Reporter | |
Comment 1•8 years ago
|
||
This issue is only reproducible on master as the Top Tabs for iPad feature is not yet released. The feature is enabled only on master.
|
Assignee | |
Updated•8 years ago
|
|
|
Assignee | |
Updated•8 years ago
|
|
|
Assignee | |
Comment 2•7 years ago
|
||
crash be gone! master https://github.com/mozilla-mobile/firefox-ios/commit/51c7e1dbd2ee4ee0463ebf5e9867454a69840412
Assignee: nobody → fpatel
Status: NEW → RESOLVED
Iteration: --- → 1.13
Closed: 7 years ago
Priority: P3 → P1
Resolution: --- → FIXED
|
|
Reporter | |
Comment 3•7 years ago
|
||
I am still able to reproduce this issue following the steps from the description on latest master 51abcc7ca.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|
||
Updated•7 years ago
|
Flags: needinfo?(fpatel)
|
|
||
Updated•7 years ago
|
Whiteboard: [MobileAS] → [MobileCore]
|
|
Assignee | |
Comment 5•7 years ago
|
||
I've got a new PR to fix this. Its on Bug 1315627
Flags: needinfo?(fpatel)
|
|
Assignee | |
Comment 6•7 years ago
|
||
Give it a shot! https://github.com/mozilla-mobile/firefox-ios/commit/4eaadbb9fc4687ed19c75b7e34bdf2ecf4404776
Status: REOPENED → RESOLVED
Iteration: 1.13 → 1.16
Closed: 7 years ago → 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•