Switching profile sometimes persists other profile

Vlad

esiayo Can you show a video of this bug?

esiayo

Vlad Sure, when i manage to reproduce the problem, because i haven't been able to rule out why it happens, it just happens randomly

esiayo

Vlad here, reproduced.

and no, the signins aren't the same on both profiles

antoineco

What happened? How did it happen?

Given two profiles, for instance Work (default) and Home, the Home profile occasionally opens with the storage of the Work profile (cookies, sessions, cache).

The issue can be recognized by:

Navigating to a website where the user was previously logged in in the selected profile but not in the other profile, and currently isn't.
Navigating to a website where the user was not previously logged in in the selected profile but was in the other profile, and currently is.
Navigating to a website where the user was logged in with a different account in both profiles, and showing the wrong account (e.g. Google showing the user work@example.com as logged in in the Home profile instead of home@example.com).

The issue cannot be reproduced consistently, but I ran into it both in 0.99.129.1.1-rc and 0.99.128.2.1-beta on separate occasions.

I ran into this issue both when opening my Home profile through:

The macOS dock (right click > Profiles > Home), with Orion not running.
The profile selector on the left of the address bar, with Orion already running.

I have not checked whether the issue could be reproduced in any direction, or if it was always the default profile "leaking" into another profile.

What did you expect to happen?

A profile consistently opens with the storage associated with that profile, never with the storage associated with a different profile.

Orion version(s)

0.99.129.1.1-rc + 0.99.128.2.1-beta
Sequoia (15)

esiayo

i've been saying this here: https://orionfeedback.org/d/8905-switching-profile-sometimes-persists-other-profile
but the developer marked it as clarification fsr

antoineco

esiayo Thanks, this seems to be the same issue indeed. For some reason your issue didn't pop in my results, or was shadowed by unrelated issues.

antoineco

I can actually reproduce this fairly reliably, but it takes a few attempts.

Open the default profile (blue icon), then open the secondary profile (orange icon)

Below, you can observe that I am logged in at orionfeedback.org in the secondary profile. (Meanwhile, I am not logged in at orionfeedback.org in the default profile.)
Quit the secondary profile with Command-Q. Then reopen, quit, reopen, ... until the issue manifests itself.

It took about 10 attempts for me this time, which roughly matches the frequency at which I run into this bug.
Notice that all sessions are from the default profile, not the secondary profile. (Side note: the browsing history is the one of the secondary profile though.)

Below, I am not longer logged in at orionfeedback.org, but I am at my work's Atlassian account.

I was however not able to reproduce the issue in the other direction, by opening the default profile from the secondary profile. I tried about 30 times in a row. I think this is a good indicator that it's always the default profile leaking into a secondary profile, never the other way around.

drtz

antoineco

I think this is a good indicator that it's always the default profile leaking into a secondary profile, never the other way around.

I can confirm it's always the primary profile storage leaking into other profiles. I've seen this problem off and on over the last few months.

Another note: you don't have to have the primary profile open and then load another profile. Loading the secondary profile from an application shortcut directly to that profile will sometimes trigger this as well. As will switching from a secondary profile to a third profile.

It's always the primary profile storage that leaks, though, regardless of which profile is opened and where it's opened from.

glhrmv

Recently experienced this as well - no clue how it happened but it's very disconcerting.

JeremyHiggs

+1 to this. It's also resulted in the extensions in the non-default profile being "reset" to the extensions in the default profile.

Vlad

@JeremyHiggs @glhrmv @drtz Any discrete steps to reproduce the problem?

glhrmv

Vlad Scenario below:

Orion window with Profile 1 (Instance 1) open
Orion window with Profile 2 (Instance 2) open

If Instance 1 crashes for any reason, a dialog box appears with a button to "Reopen" Orion. If reopened, the new instance will look like it's on Profile 1 (i.e. will show bookmarks, pinned tabs, etc. exclusive to Profile 1) but it will actually be using the cache/cookies of Profile 2. I verified this by opening Gmail and seeing which account was logged in.

To resolve this, I had to quit both instances of Orion (instance 2 and the newly reopened instance 1) then start a new instance of Profile 1 and open a new instance of Profile 2 from it.

For reference, Profile 2 in this scenario is my Synced profile, and Profile 1 is my Default profile.

I wish I could reproduce this further and help diagnose better but I don't know of any easy way to trigger a crash on demand.

JeremyHiggs

Vlad Apologies, I didn't seem to get an email notification for this. I have not been able to reliably reproduce it. I had the default profile open and a secondary one did not have the app open. I opened the secondary profile and noticed that the extensions in the toolbar had changed. The history is there, as are logins, etc, but the secondary profile's extensions (what's installed & active) have been replaced by the default profile's extensions. Additionally, if I re-install in the secondary profile one of the extensions that disappeared, it is restored to the previous status (so the storage isn't wiped)... it's just that the Orion profile forgets that it's installed.

antoineco

@Vlad this was marked as Done but I can still reproduce on the latest RC (0.99.131.2-rc, March 3).
When I open my "Home" profile, I'm occasionally logged into websites with my accounts from the "Work" (default) profile.

glhrmv

Interestingly, I haven't experienced this bug since last month's fix. I was getting it pretty often when I last commented.

antoineco

glhrmv admittedly this seems to occur less often than before on my end as well.