I tried to reproduce the steps but I was not able to. I am now not sure how I was able to get it into a state where CTRL+SHIFT+N was opening a new window with it auto connecting to the current window. It was an old running window that has been open for days and going through multiple sleep cycles. I will try to respond here if it happens again and I have more information on how to reproduce.

i've seen the behavior you describe once or twice, but i wasn't able to narrow down the failing scenario.  so it's def a bug that exists even if we haven't quite figured out how to make it reproducible :).

This issue seems to happen frequently after some sort of disconnect and reconnect after my machine goes to sleep. One thing that I have found is that if you continue to select "reconnect" the problem persists but if you select "choose another connection" then the problem stops for the time being.

the current code relies on opening a new window using the existing location (which includes the #profile-id marker), and i think the session state is set such that it normally skips parsing.  i dislike that logic (since it causes issue 760741), so i'll replumb the ctrl+shift+n logic so it always calls the main page.  that'll address both these issues i think even if we can't narrow down the exact reproduction.

Hopefully that also solves pressing CTRL+SHIFT+N while in the main page causing an incognito window to open.

heh, that's a completely different issue, and something i've kind of ignored.  i've moved that to  issue 771864  if you want to follow it.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot