Closed
Bug 1268033
Opened 8 years ago
Closed 8 years ago
Firefox becomes unresponsive when updating to 4.0.0b4
Categories
(Firefox for iOS :: General, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: SimonB, Assigned: sleroux)
References
Details
(Keywords: regression)
Build: 4.0.0b4 Steps to reproduce; 1. Start a browsing session in Firefox 4.0.0b3 2. Background Firefox 3. Update to Firefox 4.0.0b4 via Testfilght Actual results: - Firefox becomes unresponsive and no browsing session can be started( no page is loaded) Note: - This issue dose not occur with a clean install
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → sleroux
Status: NEW → ASSIGNED
Comment 1•8 years ago
|
||
Same here, running on an iPad, iOS 9.3.2 (beta), upgraded from 4.0.0b3. I can try to open one or two tabs, without any of them loading and than the entire app becomes unresponsive.
Updated•8 years ago
|
Assignee | ||
Comment 2•8 years ago
|
||
I was able to reproduce with a resigned version of the TestFlight build. Happened on the third time I upgraded from b3->b4. Nothing in the logs shows anything concerning though. The behavior I'm seeing is the web session fails to load the page, the toolbar items become unresponsive, and upon opening new tabs, the app eventually becomes full unresponsive.
Assignee | ||
Comment 3•8 years ago
|
||
Change list between b3 and b4: https://github.com/mozilla/firefox-ios/compare/a5ee3a8aef0793c23f78d856c0eb554cae169457...v4.x
Updated•8 years ago
|
Keywords: regression
Updated•8 years ago
|
Whiteboard: [needsuplift]
Comment 5•8 years ago
|
||
build 5 fixes this for me.
Reporter | ||
Comment 6•8 years ago
|
||
Tested on build 4.0.0b5 The issue no longer occurs when updating from 4.0.0b3 to 4.0.0b5.
Assignee | ||
Comment 7•8 years ago
|
||
Good to hear. Should be fixed from the uplift on https://github.com/mozilla/firefox-ios/commit/3ebe958d25a6f467cfd980f39dd24e2e16fc4c9d. Marking as resolved.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-fxios-v5.0:
--- → fixed
Resolution: --- → FIXED
Whiteboard: [needsuplift]
Assignee | ||
Updated•8 years ago
|
Comment 8•8 years ago
|
||
What bug fix was the cause of the regression?
Assignee | ||
Comment 9•8 years ago
|
||
As part of the core telemetry work we uplifted to the 4.0 branch, we set values on the profile from a background thread on app launch: App Launch: https://github.com/mozilla/firefox-ios/commit/f719ed1df1c4de2a2c412ffa5e5cef10574150a3#diff-19fd1a6fe4b2f78eb457726f366733e0R152 Profile modification: https://github.com/mozilla/firefox-ios/commit/f719ed1df1c4de2a2c412ffa5e5cef10574150a3#diff-682af20e99900ae1d9196b24f2f17db9R25 This normally is fine but what was happening is upon setting a value to the profile, a notification is broadcasted across the app. In this case, our TabManager was listening to this nofication: https://github.com/mozilla/firefox-ios/commit/3ebe958d25a6f467cfd980f39dd24e2e16fc4c9d. The problem is that this notification is handled on a background thread and we access the web view from it which breaks things since the web view/UIKit is not thread safe.
Reporter | ||
Updated•8 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•