Connector & Chrome debugging port

replied on April 2, 2020

Hi Glenn,

You have to enable debugging port when using Connector in Chrome. Could you provide more details about your issue when enabling the debugging port?

0 0

View 3 previous replies

replied on April 13, 2020

Hello Tianxia - Sorry for the late reply on this. I have done a little more research and tested using UI controls rather than JS and the issue has not changed. We were thinking that the problem was with having the debugging port opened. Basically, when Connector is active and displaying the button on the screen, the html application becomes very sluggish, slow to load, and occasionally non responsive causing Chrome to crash. When I go to the developer's console, I am not seeing any type of errors, just a drastic reduction in speed to the page.

0 0

replied on April 13, 2020

Hi Glenn,

Please try the following steps which will help us to identify the root cause of your issue:

1. Exit Connector in the tray menu and make sure no button will be shown on specific websites you have configured.

2. Close all Chrome tabs, and make sure no chrome.exe in the task manager -> details tab

3. Open the command prompt, using the following command line to launch Chrome with the port used by Connector.

Note: (1) If you installed Chrome in a different place, please use the file path where you installed the Chrome; (2) If you have changed your default port of Connector, please replace 9222 with the updated port number.)

C:\Users\tianxia.wang>cd "\Program Files (x86)\Google\Chrome\Application"
C:\Program Files (x86)\Google\Chrome\Application>chrome --remote-debugging-port=9222

4. Go to the task manager, and make sure your Chrome is opened using remote-debugging-port.

5. Go to the websites you meet issues and see if the websites are still slow and occasionally nonresponsive causing Chrome to crash.

0 0

replied on April 14, 2020 • Show version history

Hello Tianxia - Initially I had followed the instructions above and enabled the remote debugging port. Once we saw the speed and Chrome crashing issue, our first thought was it was something to do with the debugging port being enabled. I then re-created my profiles using UI controls rather than js so that they would work without the debugging port enabled. Now I am seeing the issue both with and without the debugging port enabled. I am seeing this is on approximately 55 users, on Windows 10 machines, running Chrome version 81.0.4044.92.

0 0

replied on April 15, 2020

Hi Glenn,

Thanks for your information. Will you still meet the issue after exiting the Connector (UI control or js)? Is that possible to share the websites you meet issues? Can we access it and make some tests?

0 0

replied on April 15, 2020

Hello Tianxia - Yes, Once we exit Connector, the issue is no longer present. I would be happy to share the website, but it is internal to our network, hosted locally on an internal web server. I would be more than willing to schedule a webex to share the screen and site for you to make your tests, i will make myself available any time you may have available. Please feel free to reach out at any time. My email address is glenn.williams@tcectexas.com

Thank you!

Glenn

0 0

replied on April 15, 2020

Hi Glenn, in this case, I recommend you (or your solution provider) to create a support case, provide log files and profiles (it would be better if you can save your website as an HTML file and send it to us too), since it would be more helpful that dev team spent some time investigating based on these files and trying to find some clues before troubleshooting on your environment directly.

0 0

Question

Question

Connector & Chrome debugging port

Replies

Sign in to reply to this post.