Switching profile sometimes persists other profile
- Edited
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.
- Edited
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.
Recently experienced this as well - no clue how it happened but it's very disconcerting.
+1 to this. It's also resulted in the extensions in the non-default profile being "reset" to the extensions in the default profile.
@JeremyHiggs @glhrmv @drtz Any discrete steps to reproduce the problem?
- Edited
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.
- Edited
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.
Interestingly, I haven't experienced this bug since last month's fix. I was getting it pretty often when I last commented.