-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Crash in settings_overridden_params::GetSearchOverriddenParams #14218
Comments
maybe related to #15140 |
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Changed to use same TemplateURLService for normal & private profile.
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Changed to use same TemplateURLService for normal & private profile.
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Changed to use same TemplateURLService for normal & private profile.
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.
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.
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.
Verified
I confirmed both the functionality is correct, as well as -- more importantly for this issue -- that I didn't have any crashes 👍 Steps:
Verification passed on
Verification passed on
Extension was unable to change default search engine in Normal Window nor Private Window. Logged #16227 |
Testing brave/brave-core#8626 will cover the following issues: |
https://brave.sp.backtrace.io/p/brave/triage?filters=((callstack.functions%2Ccontains%2CGetSearchOverriddenParams)%2Cptype%3Dbrowser)&aggregations=((channel%2Cdistribution%2C3)%2C(ptype%2Chead)%2C(uname.sysname%2Cdistribution%2C3))
The text was updated successfully, but these errors were encountered: