Non-Regression: Chrome crashes with UI glitch is seen for second user when "enable-virtual-keyboard-md-ui" flag is enabled in owner account |
||||||||
Issue descriptionChrome Version: 70.0.3508.3/10930.00 dev-channel Daisy,Kip,Celes OS: What steps will reproduce the problem? (1)Sign into user >>Enable "enable-virtual-keyboard-md-ui" flag for new UI of virtual keyboard (2)Enable virtual keyboard from ubertray/Accessibility (3)Sign out of the user >> In temp web ui..screen >>click on Add person (4) Add a second user and observe crash with UI glitch after you're signed in screen(Please refer video) Actual: Crash with UI glitch is seen after adding second user Expected: No such crash or glitches should be seen Raising this as a Non-Regression issue as "enable-virtual-keyboard-md-ui" flag is a new Note: ----- 1.Issue is only seen when we enable "enable-virtual-keyboard-md-ui" flag for new UI of virtual keyboard 2.Issue is also seen in M-69 dev Crash Ids: ----------- e01173a5215f6847 f96790bd8b027595 c50b60e2f1563957 Stack Trace: ------------ Thread 0 (id: 0x2725) CRASHED [SIGSYS @ 0x00000000 ] MAGIC SIGNATURE THREAD Stack Quality93%Show frame trust levels 0xb6f27816 (ld-2.23.so + 0x00011816 ) __libc_do_syscall 0xb6f169f1 (ld-2.23.so -rtld.c:632 ) init_tls 0xb6f185f9 (ld-2.23.so -rtld.c:1719 ) dl_main 0xb6f26ea1 (ld-2.23.so -dl-sysdep.c:249 ) _dl_sysdep_start 0xb6f19cb7 (ld-2.23.so -rtld.c:307 ) _dl_start 0xb6f16a8d (ld-2.23.so + 0x00000a8d ) _start 0xb6f4130f (dash + 0x0000130f ) _init Link to the list of builds: --------------------------- https://crash.corp.google.com/browse?q=expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27init_tls%27+AND+product_name%3D%27ChromeOS%27 As there is no relevant file seen in Stack trace, so cant assign it to its right owner. But the crash seems to be related to "enable-virtual-keyboard-md-ui" flag, so cc'ing the respective devs of virtual keyboard component. Flag is seen from M-69 and resulting in browser crash .Hence, adding Stable Blocker.
,
Aug 2
Passing to the owner of the flag
,
Aug 2
Can't seem to repro on 70.0.3511.0 Eve. Three questions: 1. Does the bug repro reliably? 2. Is step 2) of the repro instructions necessary? From the video, it seems like you opened the keyboard and then dismissed it. 3. Does the bug only happen when you add a user, or does it also happen when there's already a second user and you just log in?
,
Aug 3
As of now,latest available ToT in GE is 70.0.3508.3/10933.0.0 dev .Able to reproduce the issue on this build. Will recheck and update the issue once build >70.0.3508.3 is available. 1.Yes,the bug repro reliably. 2.Step (2) is not necessary 3.It also happen when there's already a second user and you just log in. Thanks!
,
Aug 3
Ok, thanks! I'll keep trying to reproduce.
,
Aug 22
Hi is this crash still reproducible? The crash graph seems to show that the number of crashes has decreased to almost zero?
,
Sep 4
Tested the issue on 70.0.3538.0/11031.0.0 dev,able to reproduce the crash with the UI glitch. Thanks!
,
Sep 4
Still can't repro on 70.0.3535.0. I did the following: 1) Logged into a user. 2) Went to chrome://flags 3) Turned on enable-virtual-keyboard-md-ui 4) Clicked restart 5) Confirmed that the flag is enabled 6) Signed out 7) Logged into second user 8) No weird glitches seen Does the bug repro even if you don't enable the flag (i.e. leave it as "Default")? From 70 onwards, enable-virtual-keyboard-md-ui is enabled by default, so if it's a problem with the flag being enabled, then the crash should repro without turning on any flags. Thanks!
,
Sep 5
C #8 > 1.Bug doesn't repro when we dont enable the flag(i.e. leave it as "Default") 2.Bug repro's only when enable-virtual-keyboard-md-ui flag is enabled please find the attached screencast for reference.. Thank you!
,
Oct 1
Friendly ping, please provide an update on this issue. Is this still RBS (if not please remove the label)? When is the ETA on the work that needs to be done to resolve this? Thanks.
,
Oct 1
Sorry, but I can't reproduce this at all. This is very weird because the flag is "on" by default in from M70 onwards, so changing the flag to "enabled" doesn't do anything at all. Removing RBS label.
,
Nov 8
Going to close this one...the new UI has hit stable already and we don't have any crashes from that. The flag is no longer used. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by rkalavakuntla@chromium.org
, Aug 213.0 MB
13.0 MB View Download