As a related aside: We should not enable profiling if there exist any incognito sessions. If profiling has already been enabled, we should ensure that no traces/heap_dumps are uploaded if an incognito session exists [at least for slow reports integration. Maybe we want different behavior for explicitly enabled from chrome://flags?]
I'm confused at the incognito session exclusion. Do you mean we shouldn't
profile any renderers for an incognito session? Or do you mean we need to
disable the browser and gpu logging too?
wdyt of this:
1) If any incognito session is active, do not begin any new profiling.
2) If any incognito session is active, do not trigger any slow report uploads.
Comment 1 by erikc...@chromium.org
, Oct 24 2017