-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome browser not terminated after execution - initial fix implemented #648
Comments
Fix deployed in TagUI v5.11 packaged release - https://github.com/kelaberetiv/TagUI#set-up Solution is add an additional |
Users with with an existing installation, you may also download the cutting edge version master.zip to overwrite. Instead of downloading above packaged zip which is 150+ MB. More details here - https://github.com/kelaberetiv/TagUI#set-up |
Issue first spotted on macOS Catalina release, running Chrome Version 79.0.3945.88 (Official Build) (64-bit). Not sure if it is due to macOS update changes or Chrome update change.
Observations from macOS shows that the Chrome processes info returned have changed. Due to that, the TagUI Chrome process isn't killed properly. Adding another
grep window-size
after thegrep tagui_user_profile
seems to fix the issue. To dig further and also collect feedback.Below debugging info from macOS. Need to check on Linux and Windows. CC @siowyisheng
The text was updated successfully, but these errors were encountered: