Closed
Bug 1337822
Opened 9 years ago
Closed 9 years ago
Make SearchEngines.getUnorderedBundledEngines more robust
Categories
(Firefox for iOS :: General, defect, P3)
Tracking
()
RESOLVED
DUPLICATE
of bug 1354934
| Tracking | Status | |
|---|---|---|
| fxios | 8.0+ | --- |
People
(Reporter: st3fan, Unassigned)
Details
(Whiteboard: [MobileCore])
Attachments
(2 files)
At the end of getUnorderedBundledEngines() there is a forced unwrap, which can trigger a crash if the call above to parser.parse() failed.
It is better to not show the search engine than to crash.
| Reporter | ||
Comment 1•9 years ago
|
||
Updated•9 years ago
|
Whiteboard: [MobileCore]
| Reporter | ||
Updated•9 years ago
|
Assignee: sarentz → nobody
Comment 2•9 years ago
|
||
Attachment #8846830 -
Flags: review?(etoop)
Comment 3•9 years ago
|
||
Comment on attachment 8846830 [details] [review]
Pull Request
https://github.com/mozilla-mobile/firefox-ios/pull/2517
pull request from master.
Comment 4•9 years ago
|
||
Comment on attachment 8846830 [details] [review]
Pull Request
The fix looks good, but as it's really hard to test I'd like to see a unit test added that demonstrates that the correct response of not adding the corrupted engine actually occurs.
Attachment #8846830 -
Flags: review?(etoop) → feedback+
Comment 5•9 years ago
|
||
It's my understanding that if the parser.parse function can't parse the search engine it will return nil. Presumably if that function has a bug where it returns a malformed search engine, that would be a different bug. This fix just prevents ff from crashing when the parser can't parse a given search engine.
| Reporter | ||
Updated•9 years ago
|
Updated•9 years ago
|
Priority: -- → P3
| Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•