Closed
Bug 1183486
Opened 10 years ago
Closed 10 years ago
Repeated crash when tapping URL bar immediately after opening app (build 24)
Categories
(Firefox for iOS :: Browser, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
fxios | + | --- |
People
(Reporter: rnewman, Assigned: sleroux)
Details
(Keywords: crash)
Attachments
(2 files, 1 obsolete file)
One tab was restoring. Tap bar, crash. App relaunches. Did this multiple times.
Crash log:
https://gist.github.com/rnewman/2e791147f523172a85b4
I don't have the dSYM to symbolicate this. St3fan?
Flags: needinfo?(sarentz)
![]() |
||
Comment 1•10 years ago
|
||
Archive for Firefox 1.0 (24):
https://www.dropbox.com/s/k9gt7xfll13rvhn/Firefox%202015-07-10%2C%203.55%20PM.xcarchive.zip?dl=0
I don't know how to manually symbolicate. You may be able to simply import this xcarchive in the navigator and then drop the crash report in there too. Not entirely sure.
![]() |
||
Updated•10 years ago
|
Flags: needinfo?(sarentz)
Reporter | ||
Updated•10 years ago
|
![]() |
Assignee | |
Comment 2•10 years ago
|
||
Added symbolicated crash
![]() |
Assignee | |
Updated•10 years ago
|
Assignee: nobody → sleroux
![]() |
Assignee | |
Comment 3•10 years ago
|
||
I'm having a hard time reproducing this on latest master and build 24 from builds/AuroraV24 branch. The symbolicated crash is pointing me to L135 in HomePanelViewController where we are removing the current panel's view from the superview. I have a hard time seeing why this would crash. The only thing I can think of is that view is not allocated yet and is actually nil which is causing an explict unwrap crash. A safe fix would be to just check to see if the current panel's view even has a super view and only remove it if it's actually being shown.
Was there any other tips to reproduce this so I can reliably put the fix in?
![]() |
Assignee | |
Updated•10 years ago
|
Flags: needinfo?(rnewman)
Comment 4•10 years ago
|
||
Updated•10 years ago
|
Severity: normal → critical
![]() |
Assignee | |
Comment 5•10 years ago
|
||
Attachment #8636675 -
Flags: review?(bnicholson)
Reporter | ||
Comment 6•10 years ago
|
||
(In reply to Stephan Leroux [:sleroux] from comment #3)
> Was there any other tips to reproduce this so I can reliably put the fix in?
Just hurrying, really. Timing-related bugs are a bear.
Flags: needinfo?(rnewman)
Reporter | ||
Updated•10 years ago
|
Status: NEW → ASSIGNED
Comment 7•10 years ago
|
||
Comment on attachment 8636675 [details] [review]
PR https://github.com/mozilla/firefox-ios/pull/778
Hm, we probably do this incorrectly in all of the other places we add/remove controllers. Think those are worth fixing too?
Attachment #8636675 -
Flags: review?(bnicholson) → review+
![]() |
Assignee | |
Updated•10 years ago
|
Attachment #8636675 -
Attachment is obsolete: true
![]() |
Assignee | |
Comment 8•10 years ago
|
||
I did a search for where we addChildViewController/removeFromParentViewController and updated those parts as well.
Attachment #8638017 -
Flags: review?(bnicholson)
Comment 9•10 years ago
|
||
Comment on attachment 8638017 [details] [review]
PR https://github.com/mozilla/firefox-ios/pull/778
Nice, hopefully this fixes the crashes!
Attachment #8638017 -
Flags: review?(bnicholson) → review+
![]() |
Assignee | |
Comment 10•10 years ago
|
||
Merged
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•