Chromium doesn't work on strange windows accounts, but chrome does

1,691 views
Skip to first unread message

Pavel Seleznev

unread,
Nov 7, 2018, 5:45:20 AM11/7/18
to Chromium-dev
Hello,

I build browser based on Chromium sources and found something strange during migration my patches from Chromium 68.0.3440.106 to Chromium 70.0.3538.77.

When I run clean build based on Chromium it can't show the main window on accounts that named as ßϗЯна'& --Life!1 on Windows 7x32/10x64
(two different code pages (German&Russian) to check proper utf8 convestion, two minus to check cmdline parser, single quote to check windows BAT file behavior and symbol & is for fun)

This is the log when I start compiled file with --enable-logging option, but it doesn't help, because if we change user name on same machine the browser will work

[3480:3192:1107/133123.768:WARNING:account_consistency_mode_manager.cc(296)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.
[3480:1604:1107/133123.889:WARNING:discovery_network_list_win.cc(195)] Failed to open Wlan client handle: 1062
[3480:3192:1107/133123.912:WARNING:account_consistency_mode_manager.cc(296)] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.
[3480:3192:1107/133124.143:ERROR:input_method_base.cc(146)] NOT IMPLEMENTEDUsing InputMethodKeyboardControllerStub
[668:1640:1107/133124.208:ERROR:gl_surface_egl.cc(538)] EGL Driver message (Critical) eglInitialize: No available renderers.
[668:1640:1107/133124.209:ERROR:gl_surface_egl.cc(953)] eglInitialize D3D11 failed with error EGL_NOT_INITIALIZED, trying next display type
[3480:3192:1107/133124.252:WARNING:external_registry_loader_win.cc(235)] Error observing HKLM: 5
[668:1640:1107/133125.406:ERROR:gl_surface_egl.cc(538)] EGL Driver message (Critical) eglInitialize: No available renderers.
[668:1640:1107/133125.407:ERROR:gl_surface_egl.cc(953)] eglInitialize D3D9 failed with error EGL_NOT_INITIALIZED
[668:1640:1107/133125.408:ERROR:gl_initializer_win.cc(196)] GLSurfaceEGL::InitializeOneOff failed.
[668:1640:1107/133125.457:ERROR:viz_main_impl.cc(184)] Exiting GPU process due to errors during initialization
[4028:2708:1107/133133.840:ERROR:gl_context_egl.cc(199)] eglCreateContext failed with error EGL_BAD_ALLOC
[2508:3028:1107/133134.276:ERROR:gl_context_egl.cc(199)] eglCreateContext failed with error EGL_BAD_ALLOC
[2880:4076:1107/133134.570:ERROR:gl_context_egl.cc(199)] eglCreateContext failed with error EGL_BAD_ALLOC


I have commented SetFileUrlPathAliasForIpcFuzzer function because it provide path to compiled to cmdline but it doesn't help

I suppose that something was changed since 68.0.3440.106 but I don't have idea where to dig. Any thoughts?

Regards,
Pavel

Greg Thompson

unread,
Nov 7, 2018, 6:18:31 AM11/7/18
to pavel.s...@gmail.com, chromi...@chromium.org
Does a recent Chromium snapshot (see https://www.chromium.org/getting-involved/download-chromium) exhibit the same behavior? If so, you could file a bug with the simplest repro steps you can devise. Otherwise, I'm afraid you'll need to do some debugging. :-) Is the browser crashing? If you run in your debugger of choice, do you see a crash with a meaningful stack?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/1e53a9c8-5490-45a4-bd8d-8b54240c4fd5%40chromium.org.

Pavel Seleznev

unread,
Nov 7, 2018, 6:30:49 AM11/7/18
to Chromium-dev, pavel.s...@gmail.com
Download recent Chromium snapshot and get the same behavior, so I will file a bug

среда, 7 ноября 2018 г., 14:18:31 UTC+3 пользователь Greg Thompson написал:
Reply all
Reply to author
Forward
0 new messages