-
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 when searching via private window while having SE extension set as Allow in private
#15224
Comments
Allow in private
This isn't a new regression, @simonhong mentioned that he can reproduce the crash in
Probably not a |
Reproduced the issue in
and
|
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
Steps:
Verification passed on
Verification passed on
|
Added |
Testing brave/brave-core#8626 will cover the following issues: |
Description
When you have a SE extension installed and have set it as
Allow in Private
, searching for a term via private mode will crash the entire browser. Similar to the issue that was fixed via #15140.d5250000-9cfd-2306-0000-000000000000
d4250000-9cfd-2306-0000-000000000000
d3250000-9cfd-2306-0000-000000000000
Steps to Reproduce
brave://extensions
and set DDG Privacy Essentials asAllow in private
by clickingDetails
test test
and clickenter
to start the searchActual result:
Brave instantly crashes.
Expected result:
Brave shouldn't be crashing.
Reproduces how often:
100% reproducible using the above STR.
Brave version (brave://version info)
Version/Channel Information:
Yes
Yes
Yes
Other Additional Information:
N/A
N/A
N/A
Miscellaneous Information:
CCing @rebron @bsclifton @simonhong @brave/legacy_qa
The text was updated successfully, but these errors were encountered: