New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 846129 link

Starred by 2 users

Issue metadata

Status: Closed
Owner:
please use my google.com address
Closed: Aug 7
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

ERROR:services/service_manager/service_manager.cc(942) "Failed to resolve service name: ui"

Project Member Reported by sebmarchand@chromium.org, May 23 2018

Issue description

Hi,

I just did a fresh ToT build of Chrome (@659f4ca4) on Windows with the following
GN args:
    is_debug = true
    is_component_build = true
    enable_nacl = false
    target_cpu = "x86"
    remove_webcore_debug_symbols = true
    symbol_level = 2
    is_win_fastlink = true
    use_goma = true
    goma_dir = "C:\src\goma"
    is_clang = true
    win_console_app = true

And when running it with the "--enable-logging --v=0" flags I see the following
message printed in the console:
[14252:21240:0523/182831.162:service_manager/service_manager.cc(942)] Failed to resolve service name: ui

Git blame tells me that you're the author of this message, could you please look
into it (or find an appropriate owner)? (note that this seems related to  crbug.com/846127 )

Thanks!
 
 
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Status: Closed (was: Assigned)
I don't think this is still an issue.

Sign in to add a comment