-
Notifications
You must be signed in to change notification settings - Fork 895
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixed crash with search extension #8626
fixed crash with search extension #8626
Conversation
3a7b61f
to
7870a76
Compare
35b5f46
to
c3e213a
Compare
d207e41
to
c66ba27
Compare
c66ba27
to
6b9aaa1
Compare
6b9aaa1
to
322f3b2
Compare
browser/search_engines/tor_window_search_engine_provider_service.cc
Outdated
Show resolved
Hide resolved
322f3b2
to
bf9af23
Compare
Kindly ping :) |
I'll defer to @goodov |
browser/search_engines/tor_window_search_engine_provider_service.cc
Outdated
Show resolved
Hide resolved
browser/search_engines/tor_window_search_engine_provider_service.h
Outdated
Show resolved
Hide resolved
bf9af23
to
a76d539
Compare
a76d539
to
7a0d11b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@goodov Thanks for review. All addressed!
browser/search_engines/tor_window_search_engine_provider_service.h
Outdated
Show resolved
Hide resolved
browser/search_engines/tor_window_search_engine_provider_service.cc
Outdated
Show resolved
Hide resolved
@simonhong |
@goodov Thanks for sharing DCHECK failure. Failure from |
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Crash comes from absense of exension search provider data in private profile's TemplateURLService because we are using different TemplateURLService for private profile. When search provider extension is loaded/installed, browser doesn't notify about this adding to private profile's TUS. To fix this, each SearchEngineProviderService sets extension's template url data to its service when normal profile's search provider comes from extension.
131c9aa
to
d091ba7
Compare
|
Still doesn't seem right. After disabling the Extension search engine via Settings and enabling extension manually I got this error: https://gist.github.com/goodov/58a34a9ed19350984a9454b6522cae4d |
d091ba7
to
e4316b3
Compare
Fixed by https://github.com/brave/brave-core/pull/8626/files#diff-303c4f4e4e368bfb2681efc54ff35e1412d362740939fc50c7f93b9b92bcca2cR139. Changed to setting non-empty sync_guid. This PR will work :) Thanks for catching this. And I'm trying another approach - This PR added new patches because we didn't make |
latest version seems fine, no any visible issues and the logic works great!
so should we wait for solution without patching? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved, but please follow-up as discussed to see if we can get rid of the patch
Merged because only unrelated brave ads/rewards browser tests were failed. |
fix: brave/brave-browser#15224
fix: brave/brave-browser#10601
fix: brave/brave-browser#14218
With this PR, brave uses search provider from extension by default on all platform like chromium does.
Crash comes from absense of exension search provider data in private profile's TemplateURLService because
we are using different TemplateURLService for private profile. When search provider extension is loaded/installed, browser doesn't notify about this adding to private profile's TUS.
To fix this, each SearchEngineProviderService sets extension's template url data to its service when normal profile's search provider comes from extension.
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
,npm run lint
,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan:
npm run test brave_browser_tests -- --filter=*ExtensionSearchProviderWithPrivateWindow*
Allow in private
repeatedlyAllow in privatge
option doesn't affect private window's search provider - still using ecosia