|
|
Chromium Code Reviews|
Created:
4 years, 3 months ago by manzagop (departed) Modified:
4 years, 3 months ago Reviewers:
grt (UTC plus 2) CC:
chromium-reviews Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionInvestigate RelaunchChromeBrowserWithNewCommandLineIfNeeded log spam
BUG=648185
Committed: https://crrev.com/c5442858e4f80adbd8afe5dfcfee95b4aba1d487
Cr-Commit-Position: refs/heads/master@{#419889}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Print the process type instead #Messages
Total messages: 17 (9 generated)
manzagop@chromium.org changed reviewers: + grt@chromium.org
Please have a look? Thanks! Pierre
Thanks for looking at this so quickly! https://codereview.chromium.org/2351533004/diff/1/chrome/app/chrome_exe_main_... File chrome/app/chrome_exe_main_win.cc (right): https://codereview.chromium.org/2351533004/diff/1/chrome/app/chrome_exe_main_... chrome/app/chrome_exe_main_win.cc:247: if (process_type.empty()) { it feels cleaner to me for this function to know as little as possible about how different process types operate. wdyt about putting this logic in MainDllLoader?
Description was changed from ========== Only attempt a browser relaunch from the browser process BUG=648185 ========== to ========== Investigate RelaunchChromeBrowserWithNewCommandLineIfNeeded log spam BUG=648185 ==========
Sorry for the slow turnaround. :( As per the discussion on the bug, I switched to simply printing the process type, since we're not sure which is the cause of the spam. Another look? Thank! https://codereview.chromium.org/2351533004/diff/1/chrome/app/chrome_exe_main_... File chrome/app/chrome_exe_main_win.cc (right): https://codereview.chromium.org/2351533004/diff/1/chrome/app/chrome_exe_main_... chrome/app/chrome_exe_main_win.cc:247: if (process_type.empty()) { On 2016/09/19 19:59:42, grt (UTC plus 2) wrote: > it feels cleaner to me for this function to know as little as possible about how > different process types operate. wdyt about putting this logic in MainDllLoader? Sgtm.
The CQ bit was checked by manzagop@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
On 2016/09/20 20:11:52, grt (UTC plus 2) wrote: > lgtm Thanks for the review!
The CQ bit was checked by manzagop@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Investigate RelaunchChromeBrowserWithNewCommandLineIfNeeded log spam BUG=648185 ========== to ========== Investigate RelaunchChromeBrowserWithNewCommandLineIfNeeded log spam BUG=648185 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Investigate RelaunchChromeBrowserWithNewCommandLineIfNeeded log spam BUG=648185 ========== to ========== Investigate RelaunchChromeBrowserWithNewCommandLineIfNeeded log spam BUG=648185 Committed: https://crrev.com/c5442858e4f80adbd8afe5dfcfee95b4aba1d487 Cr-Commit-Position: refs/heads/master@{#419889} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/c5442858e4f80adbd8afe5dfcfee95b4aba1d487 Cr-Commit-Position: refs/heads/master@{#419889} |
