Can you elaborate on "it decides to create a new user". What happened exactly? Did this happen at the same time the bug reporting interface displayed or after it was submitted?

Meaning at the same time the bug reporting interface displayed when clicking report a bug in Chrome Canary, a new user gets created.

Thank you for providing more feedback. Adding requester "lgrey@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Thanks for responding! 

Unfortunately I'm still not clear on what "a new user gets created" means. Do you mean a new Chrome profile or some other kind of "user"? What do you see that indicates something was created?

New chrome profile gets created. Whenever I click on report a bug, before the report bug interface displays a whole new chrome canary window opens with another profile called person 1

Thank you for providing more feedback. Adding requester "lgrey@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Weird!

1) This is via Help > "Report an issue", correct?
2) Does this sign you out of your original window? If not, does "Person1" now appear in the profile switcher? If yes, does your original profile appear in the profile switcher?
3) (Shot in the dark) Can you tell if a second Canary instance appears in the Dock, either briefly or permanently when this happens?

1. Correct. Also happens from the About Google Chrome page and then clicking on report a bug button there as well. 

2. It does not sign me out of my original window. “Person1” does show in the profile manager. My regular profile is also still in the profile manager. 

3. It doesn’t appear that another Canary instance appears on the dock. It’s only showing one chrome canary on the dock. I’m not sure if it does happen temporarily to the point of it showing a second one and then immediately, but as I have observed I haven’t seen a second instance of Canary on the dock.

Thank you for providing more feedback. Adding requester "lgrey@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Strongly suspect crbug/803643 but not quite ready to call it a dupe. I'm curious if this persists after the change is reverted (so, hopefully tomorrow's Canary).

I guess, whatever else is occurring causes Chrome Canary to crash if I retry to use the report an issue feature. I copied a crash log from the Google Chrome Quit Unexpectedly window.

Deleted: crashed.txt 118 KB

crashed.txt 118 KB View Download

That crash information I attached happened when I attempted to go into the report a bug interface for the second time. 

Able to reproduce this issue on reported canary 66.0.3335.5 and latest canary 66.0.3336.5 using Mac 10.13.3. But issue is not reproducible on equivalent dev build. As issue is not reproducible on dev builds it will not be possible to provide bisect info. Hence removing Needs-Bisect label and marking as Untriaged.

NOTE: Issue is seen only when one profile is present. Issue is not seen on 66.0.3335.5, 66.0.3336.5 of Windows.

@lgrey:Please add Needs-Bisect if you feel so and also please have a look at crash log attached. 

cc'ing 	dullweber@ from issue 803643 for further inputs on this.

Thanks!

Deleted: crash log.rtf 112 KB

crash log.rtf 112 KB Download

This looks like my change could have caused it. The CL is reverted and the next canary should work fine. 

The stacktrace was the following:
0x0000000108fefd9a (Google Chrome Framework - profile_manager.cc: 1396)	ProfileManager::CreateAndInitializeProfile(base::FilePath const&)
0x0000000108fef89d (Google Chrome Framework - profile_manager.cc: 505)	ProfileManager::GetProfile(base::FilePath const&)
0x0000000108fef7ff (Google Chrome Framework - profile_manager.cc: 1363)	ProfileManager::GetActiveUserOrOffTheRecordProfileFromPath(base::FilePath const&)
0x0000000109061be8 (Google Chrome Framework - chrome_internal_log_source.cc: 168)	system_logs::ChromeInternalLogSource::PopulateSyncLogs(std::__1::map<std::__1::basic_string<char, std::__1::char_traits<char>, 

Because I changed GetProfile() to not return deleted profiles anymore, it would try to recreate the profile. 

I wonder why ProfileManager::GetActiveUserOrOffTheRecordProfileFromPath is returning the "default" profile. Accessing sync logs from a deleted profile sounds like a bad idea. Isn't the last used profile more interesting for feedback reports or is there some other reason for getting sync logs from the default profile? 

[mac triage] taking out of triage. sounds like this is resolved -> dullweber@ to check

yes, it's fixed