in-process-gpu command line option resulting in a hang on startup
Reported by
oetu...@nvidia.com,
Apr 10 2018
|
|||||
Issue descriptionChrome Version: 67.0.3393.0 (64-bit Canary) OS: Windows 10 What steps will reproduce the problem? (1) Run chrome.exe with command line argument --in-process-gpu What is the expected result? Chrome starts and runs the GPU service in-process. What happens instead? Chrome hangs on startup, no window appears. This seems to happen both with the release version of Chrome 65.0.3325.181 and the Canary version. Seen on two different systems with an NVIDIA and Intel GPU. This makes it difficult or impossible to use some graphics debugging tools.
,
Apr 23 2018
I have a CL to fix some issues in in-process-gpu mode: https://chromium-review.googlesource.com/c/chromium/src/+/1024859 However, I suspect even with the CL, it won't fix the issue on your side. Unfortunately I can't reproduce it on my side (Win10, NVIDIA Quadro K2200) Olli, can you try with --user-data-dir=SOME_TEMP_FOLDER and see with a clean profile, you still experience the issue
,
Apr 24 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e21324d3d773d223d0d51859681d15e9afe00ff2 commit e21324d3d773d223d0d51859681d15e9afe00ff2 Author: Zhenyao Mo <zmo@chromium.org> Date: Tue Apr 24 18:13:06 2018 Don't collect full GPU info or D3D12/Vulkan info if in-process-gpu. Otherwise it will trigger a gl_factory.cc assertion. BUG= 831168 TEST=chrome --in-process-gpu R=oetuaho@nvidia.com Change-Id: Ib50dd4350619d516d88bb30412d84a0f2644f1d5 Reviewed-on: https://chromium-review.googlesource.com/1024859 Reviewed-by: Chris Blume <cblume@chromium.org> Commit-Queue: Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/master@{#553201} [modify] https://crrev.com/e21324d3d773d223d0d51859681d15e9afe00ff2/content/browser/gpu/gpu_data_manager_impl_private.cc
,
Apr 24 2018
Olli, I am closing this as Fixed because it works on my side with this CL landed. Please use Top-of-tree build or wait a day or two for Canary to include this CL, and then try again. If --in-process-gpu still fails to work, then reopen this.
,
Apr 25 2018
Able to reproduce the issue on reported version 67.0.3393.0 (i.e; Chrome is not invoking when launched from terminal using chrome.exe --in-process-gpu). Hence verifying the fix on latest canary 68.0.3406.0 On launching chrome from terminal using chrome.exe --in-process-gpu in 68.0.3406.0 doesn't launch chrome. Issue is still reproducible on 68.0.3406.0(553301). Attaching screencast for your reference. @zmo: Could you please check the screencast and let us know if we miss anything. Please help in verifying the fix on latest canary. Thanks!
,
Apr 26 2018
re:comment #5: sorry for misleading you, but it seems Chrome Canary is in multiple DLL mode, for which --in-process-gpu or --single-process won't work. Olli: I tested with release build. Let me try debug build.
,
Apr 26 2018
Olli, I need your about:gpu content and the commandline switches you run Chrome to trigger this CHECK. I am able to build a top of tree Chrome debug. I run it with --in-process-gpu --user-data-dir=some_new_dir --enable-logging=stderr, and I am able to run it fine. I am on Win 10 with NVidia 375.63
,
Apr 27 2018
zmo: Is it possible for you to still also try with latest drivers? I'm not sure what else might still be different in my configuration.
,
Apr 27 2018
Sure, I'll try to install the latest driver later today and let you know how it runs. Still, the assertion you get seems unrelated to GPU, but there is always a chance of butterfly effects.
,
Apr 27 2018
--in-process-gpu is working on my Windows 10 workstation, which however does have an AMD rather than an NVIDIA GPU. Here's about:gpu. I verified in the Task Manager that there's no separate GPU process, and that WebGL is working. Graphics Feature Status Canvas: Hardware accelerated CheckerImaging: Enabled Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Rasterization: Hardware accelerated Surface Synchronization: Enabled Video Decode: Hardware accelerated Viz Service Display Compositor: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated Driver Bug Workarounds clear_uniforms_before_first_program_use decode_encode_srgb_for_generatemipmap disable_accelerated_vpx_decode disable_discard_framebuffer disable_dxgi_zero_copy_video disable_framebuffer_cmaa exit_on_context_lost force_cube_complete scalarize_vec_and_mat_constructor_args texsubimage_faster_than_teximage Problems Detected Some drivers are unable to reset the D3D device in the GPU process sandbox Applied Workarounds: exit_on_context_lost TexSubImage is faster for full uploads on ANGLE Applied Workarounds: texsubimage_faster_than_teximage Clear uniforms before first program use on all platforms: 124764, 349137 Applied Workarounds: clear_uniforms_before_first_program_use Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args ANGLE crash on glReadPixels from incomplete cube map texture: 518889 Applied Workarounds: force_cube_complete Framebuffer discarding can hurt performance on non-tilers: 570897 Applied Workarounds: disable_discard_framebuffer Use GL_INTEL_framebuffer_CMAA on ChromeOS: 535198 Applied Workarounds: disable_framebuffer_cmaa Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent) Decode and Encode before generateMipmap for srgb format textures on Windows: 634519 Applied Workarounds: decode_encode_srgb_for_generatemipmap Zero-copy DXGI video hangs or displays incorrect colors on AMD drivers: 623029 Applied Workarounds: disable_dxgi_zero_copy_video VPx decoding isn't supported well before Windows 10 creators update.: 616318, 667532 Applied Workarounds: disable_accelerated_vpx_decode Don't expose disjoint_timer_query extensions to WebGL: 808744 Native GpuMemoryBuffers have been disabled, either via about:flags or command line. Disabled Features: native_gpu_memory_buffers Viz service display compositor is not enabled by default. Disabled Features: viz_display_compositor Version Information Data exported 2018-04-27T20:23:47.923Z Chrome version Chrome/68.0.3412.0 Operating system Windows NT 10.0.14393 Software rendering list URL https://chromium.googlesource.com/chromium/src/+/4d4aa99b532b9f5685316b0fa85fd6ca50667216/gpu/config/software_rendering_list.json Driver bug list URL https://chromium.googlesource.com/chromium/src/+/4d4aa99b532b9f5685316b0fa85fd6ca50667216/gpu/config/gpu_driver_bug_list.json ANGLE commit id 467c15f970b9 2D graphics backend Skia/68 a886544a7bf727a8f0d75597df99474dcba97273- Command Line "out\Debug\chrome.exe" --in-process-gpu --flag-switches-begin --flag-switches-end --gpu-preferences=KAAAAAAAAACiAwBAAQAAAAAAAAAAAGAAEAAAAAAAAAAAAAAAAAAAACgAAAAEAAAAIAAAAAAAAAAoAAAAAAAAADAAAAAAAAAAOAAAAAAAAAAQAAAAAAAAAAAAAAAKAAAAEAAAAAAAAAAAAAAACwAAABAAAAAAAAAAAQAAAAoAAAAQAAAAAAAAAAEAAAALAAAA Driver Information Initialization time 4 In-process GPU true Passthrough Command Decoder false Direct Composition false Supports overlays false Sandboxed false GPU0 VENDOR = 0x1002, DEVICE= 0x683d *ACTIVE* Optimus false AMD switchable false Desktop compositing Aero Glass Diagonal Monitor Size of \\.\DISPLAY1 29.7" Driver D3D12 feature level Not supported Driver Vulkan API version Not supported Driver vendor Advanced Micro Devices, Inc. Driver version 22.19.662.4 Driver date 7-20-2017 Pixel shader version 5.0 Vertex shader version 5.0 Max. MSAA samples 8 Machine model name Machine model version GL_VENDOR Google Inc. GL_RENDERER ANGLE (AMD Radeon R7 200 Series Direct3D11 vs_5_0 ps_5_0) GL_VERSION OpenGL ES 2.0 (ANGLE 2.1.0.467c15f970b9) GL_EXTENSIONS GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object Disabled Extensions GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent Disabled WebGL Extensions EXT_disjoint_timer_query EXT_disjoint_timer_query_webgl2 Window system binding vendor Google Inc. (adapter LUID: 000000000001b0c7) Window system binding version 1.4 (ANGLE 2.1.0.467c15f970b9) Window system binding extensions EGL_EXT_create_context_robustness EGL_ANGLE_d3d_share_handle_client_buffer EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_surface_d3d_texture_2d_share_handle EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_ANGLE_direct_composition EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_CHROMIUM_sync_control EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled Direct rendering Yes Reset notification strategy 0x8252 GPU process crash count 0 Compositor Information Tile Update Mode One-copy Partial Raster Enabled GpuMemoryBuffers Status ATC Software only ATCIA Software only DXT1 Software only DXT5 Software only ETC1 Software only R_8 Software only R_16 Software only RG_88 Software only BGR_565 Software only RGBA_4444 Software only RGBX_8888 GPU_READ, SCANOUT RGBA_8888 GPU_READ, SCANOUT BGRX_8888 Software only BGRX_1010102 Software only RGBX_1010102 Software only BGRA_8888 Software only RGBA_F16 Software only YVU_420 Software only YUV_420_BIPLANAR Software only UYVY_422 Software only Display(s) Information Info Display[2528732444] bounds=[0,0 2560x1600], workarea=[0,0 2560x1560], scale=1, external. Color space information {primaries:BT709, transfer:IEC61966_2_1, matrix:RGB, range:FULL} Bits per color component 8 Bits per pixel 24
,
Apr 30 2018
Olli, I upgraded to the latest driver (64 bit, 397.31, Win10) on my Windows bot, and I can still run Chrome with --in-process-gpu with a new --user-data-dir. Let me post my gn args, and see if you can build with the same config and still repro this issue.
,
Apr 30 2018
is_component_build = true is_debug = true enable_nacl = false use_goma = true # remove this for non-googler goma_dir = "c:\src\goma\goma-win64" # remove this for non-googler dcheck_always_on = true target_cpu = "x86" remove_webcore_debug_symbols = true use_jumbo_build = true ffmpeg_branding = "Chrome" proprietary_codecs = true
,
Apr 30 2018
Olli, I don't know what else I can do here, since we can't reproduce the issue you have in house. A few dumb suggestions: 1) Maybe do a clean complete build vs an incremental build? 2) Switch between component build and non component build and see if the issue persistes 3) I already mentioned this, but just to emphasize, run Chrome with a new user-data-dir
,
May 3 2018
Did a clean build with the build settings above, and it works. Might be a difference between 64-bit and 32-bit build.
,
May 3 2018
OK, thanks for confirming. Mark this as Fixed for now. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by zmo@chromium.org
, Apr 10 2018Labels: -Pri-3 OS-Windows Pri-2
Owner: zmo@chromium.org
Status: Assigned (was: Untriaged)