Skip to content
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 trying to open brave://sync in private window #2852

Closed
simonhong opened this issue Jan 8, 2019 · 13 comments · Fixed by brave/brave-core#1295
Closed

Crash when trying to open brave://sync in private window #2852

simonhong opened this issue Jan 8, 2019 · 13 comments · Fixed by brave/brave-core#1295

Comments

@simonhong
Copy link
Member

simonhong commented Jan 8, 2019

Description

browser crashed when trying to load brave://sync in private window

Steps to Reproduce

Case 1.

  1. Open brave://settings
  2. Try to open brave://sync to private window via context menu
  3. Crashed

Case 2.

  1. Open private window
  2. Type brave://sync in omnibox
  3. Crashed

Actual result:

Crashed

Expected result:

brave://sync page should be opened in normal window.

Reproduces how often:

Every time

Brave version (brave://version info)

Version 0.59.20 Chromium: 72.0.3626.28 (Official Build) beta (64-bit)
Version 0.60.6 Chromium: 72.0.3626.28 (Official Build) dev (64-bit)

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?
    both. sync is not enabled in stable

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields? No
  • Is the issue reproducible on the latest version of Chrome? No

Additional Information

We need to add some brave webui to not allowing in private window rules.
Many chrome webui pages are added in that rule. So they are only opened in normal window.

@simonhong simonhong added the crash label Jan 8, 2019
@simonhong simonhong self-assigned this Jan 8, 2019
@simonhong
Copy link
Member Author

@darkdh @AlexeyBarabash Or should brave://sync be opened in private window also?

@AlexeyBarabash
Copy link
Contributor

@simonhong thanks for finding this bug.
There is no point to open brave://sync in a private window because it requires / updates the profile data. So brave://sync should not be opened in private window.

@simonhong
Copy link
Member Author

@AlexeyBarabash Ok. thanks for confirm!

@btlechowski
Copy link

btlechowski commented Jan 8, 2019

Reproduced on

Brave 0.59.20 Chromium: 72.0.3626.28 (Official Build) beta (64-bit)
Revision 997b1040b63bac324e815797ba52be0cd8f616ed-refs/branch-heads/3626@{#461}
OS Windows 7

Also reproduces for Private Window with Tor

@btlechowski
Copy link

Reproduced on Ubuntu 17.10

Brave 0.59.20 Chromium: 72.0.3626.28 (Official Build) beta (64-bit)
Revision 997b1040b63bac324e815797ba52be0cd8f616ed-refs/branch-heads/3626@{#461}
OS Linux

@simonhong
Copy link
Member Author

simonhong commented Jan 10, 2019

Also reproduced for guest window.

Loading brave://sync in private window should be redirected to normal window.
Loading brave://sync in tor/guest window should be blocked.
Also Sync sub section in settings page should be hidden in guest/tor window.

@tildelowengrimm
Copy link
Contributor

The behavior for Tor windows should match the behavior for private windows.

@simonhong
Copy link
Member Author

simonhong commented Jan 10, 2019

@tomlowenthal Do you mean loading brave://sync in tor window should be redirected to normal window as private window does?
If so, we should have policy to choose which normal profile should be used because multiple profile should be run simultaneously.
Tor/Guest profiles are completely different profile with other normal profiles. However, private profile has its own corresponding normal profile.

@tildelowengrimm
Copy link
Contributor

That's an unfortunate drawback of the current Tor implementation, and we should do everything we can to hide that implementation detail. From the perspective of the person using the browser private and Tor windows should behave identically.

@srirambv
Copy link
Contributor

@bbondy @rebron to prioritize the issue

@simonhong
Copy link
Member Author

simonhong commented Jan 15, 2019

I think this issue(and #2853) could be fixed easily after resolving brave/brave-core#1295.
I'm trying to fix all this in this week.

@rebron rebron added the priority/P3 The next thing for us to work on. It'll ride the trains. label Jan 16, 2019
@simonhong
Copy link
Member Author

simonhong commented Jan 17, 2019

Separate issue (#3003) is created for crash in tor window. Both are different issue.

@btlechowski
Copy link

btlechowski commented Feb 28, 2019

Verification passed on

Brave 0.62.8 Chromium: 73.0.3683.39 (Official Build) dev (64-bit)
Revision cc53b0e12fcaf42e4bab8d6c23bd4fb7aae99f6c-refs/branch-heads/3683@{#413}
OS Windows 7 Service Pack 1 Build 7601.24312

Test plan:
Case 1:

  1. Open brave://settings in normal window
  2. Try to open brave://sync in private window via context menu
    [PASS] Open in Private Window is disabled

Case 2:

  1. Open private window
  2. Type brave://sync in omnibox
    [PASS] brave://sync is opened in normal window

Case 3:

  1. Open private window
  2. Type brave://settings
  3. Click brave://sync link
    [PASS] brave://settings is opened in normal window

Reproduced the crash on Private Window with Tor: #3003
Reproduced the crash on Guest Window. Logged #3522

Verification passed on

Brave 0.62.26 Chromium: 73.0.3683.75 (Official Build) beta (64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Linux
  • Verified the STR mentioned in the description.
    Case 1: we cannot open brave://sync in private window via the context menu in the normal window as Open in Private Window option is disabled now.

image

Case 2: Open brave://sync in Private window opens brave sync in Normal window

Reproduced issue #3003
Reproduced issue #3522

Brave 0.62.28 Chromium: 73.0.3683.75 (Official Build) beta(64-bit)
Revision 909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS Mac OS X

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment