facebook

Debug applicaton in Chrome does not work

  1. CodeMix & Angular IDE
  2.  > 
  3. Webclipse 1.x Help
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #586675 Reply

    Fedor Losev
    Participant

    Empty page without URL is opened + timeout.

    I tried also to install fresh Angular IDE and new workspace/project, same result.

    #586691 Reply

    support-swapna
    Moderator

    Fedor,

    Sorry that you are seeing issues with debug. I checked with Angular 6 and earlier version projects but could not replicate the problem at my end.

    1. Can you please clarify if you have updated to the latest release, 2017 CI 12? If you are not working with the latest release, then please share with us the current version and build id details from Window > Preferences > Webclipse.
    2. Did the debug ever work before? Is it suddenly broken?
    3. Does the IDE switch to the Debug perspective? Please share with us any errors that are logged in the Console view during the debug session.
    3. Please share with us more details about your project, i.e the CLI version, NPM and Node.js versions.
    4. Also share with us the workspace log by clicking on the ‘Export Log’ icon in the Error Log view along with the Chrome version details.

    Apologies for inconvenience caused.

    –Swapna
    Genuitec Support

    #586701 Reply

    Fedor Losev
    Participant

    Hi Swapna,

    It happens on the latest release in my workspace but let’s save investigation on my setup:

    I install fresh Eclipse Oxygen with WTP
    Install brand-new Angular IDE from marketplace
    New Angular Project with defaults
    Start Angular server
    Click Chrome debug icon or Debug Application in Chrome

    New Chrome private instance pops out but with empty URL. Subsequently, Webclipse shows “Failed to get tabs for debugging connect timed out”.

    It did work few months before but I don’t know when it was broken. It may be broken by Chrome update, do you use latest Chrome 66.0.3359.181 to test?

    Errors in the log:

    
    java.net.SocketTimeoutException: connect timed out
    	at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
    	at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
    	at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
    	at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
    	at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
    	at java.net.PlainSocketImpl.connect(Unknown Source)
    	at java.net.SocksSocketImpl.connect(Unknown Source)
    	at java.net.Socket.connect(Unknown Source)
    	at org.chromium.sdk.internal.transport.AbstractSocketWrapper.<init>(AbstractSocketWrapper.java:35)
    	at org.chromium.sdk.internal.transport.SocketWrapper.<init>(SocketWrapper.java:27)
    	at org.chromium.sdk.internal.wip.WipBackendImpl.queryWipBrowser(WipBackendImpl.java:159)
    	at org.chromium.sdk.internal.wip.WipBackendImpl.getTabs(WipBackendImpl.java:53)
    	at org.chromium.sdk.internal.wip.WipBrowserImpl.getTabs(WipBrowserImpl.java:33)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.ChromeBrowserManager$1.selectTab(ChromeBrowserManager.java:198)
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory$3.selectVm(JavascriptVmEmbedderFactory.java:77)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.ChromeBrowserManager.openAndConnectNewTab(ChromeBrowserManager.java:90)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.JSWebAppChromeLaunchingDelegate.launch(JSWebAppChromeLaunchingDelegate.java:45)
    	at com.genuitec.eclipse.javascript.debug.core.launching.internal.JSWebAppLaunchConfigurationDelegate.launch(JSWebAppLaunchConfigurationDelegate.java:96)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
    
    
    
    org.eclipse.core.runtime.CoreException: Failed to get tabs for debugging
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory.newCoreException(JavascriptVmEmbedderFactory.java:274)
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory.access$0(JavascriptVmEmbedderFactory.java:273)
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory$3.selectVm(JavascriptVmEmbedderFactory.java:79)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.ChromeBrowserManager.openAndConnectNewTab(ChromeBrowserManager.java:90)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.JSWebAppChromeLaunchingDelegate.launch(JSWebAppChromeLaunchingDelegate.java:45)
    	at com.genuitec.eclipse.javascript.debug.core.launching.internal.JSWebAppLaunchConfigurationDelegate.launch(JSWebAppLaunchConfigurationDelegate.java:96)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
    	at com.genuitec.eclipse.modernweb.common.core.server.internal.NodejsProjectServersManagerImpl$2.run(NodejsProjectServersManagerImpl.java:483)
    	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
    Caused by: java.net.SocketTimeoutException: connect timed out
    	at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
    	at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
    	at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
    	at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
    	at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
    	at java.net.PlainSocketImpl.connect(Unknown Source)
    	at java.net.SocksSocketImpl.connect(Unknown Source)
    	at java.net.Socket.connect(Unknown Source)
    	at org.chromium.sdk.internal.transport.AbstractSocketWrapper.<init>(AbstractSocketWrapper.java:35)
    	at org.chromium.sdk.internal.transport.SocketWrapper.<init>(SocketWrapper.java:27)
    	at org.chromium.sdk.internal.wip.WipBackendImpl.queryWipBrowser(WipBackendImpl.java:159)
    	at org.chromium.sdk.internal.wip.WipBackendImpl.getTabs(WipBackendImpl.java:53)
    	at org.chromium.sdk.internal.wip.WipBrowserImpl.getTabs(WipBrowserImpl.java:33)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.ChromeBrowserManager$1.selectTab(ChromeBrowserManager.java:198)
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory$3.selectVm(JavascriptVmEmbedderFactory.java:77)
    	... 8 more
    
    

    And sometimes instead of timeout

    
    org.eclipse.core.runtime.CoreException: Failed to get tabs for debugging
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory.newCoreException(JavascriptVmEmbedderFactory.java:274)
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory.access$0(JavascriptVmEmbedderFactory.java:273)
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory$3.selectVm(JavascriptVmEmbedderFactory.java:79)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.ChromeBrowserManager.openAndConnectNewTab(ChromeBrowserManager.java:90)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.JSWebAppChromeLaunchingDelegate.launch(JSWebAppChromeLaunchingDelegate.java:45)
    	at com.genuitec.eclipse.javascript.debug.core.launching.internal.JSWebAppLaunchConfigurationDelegate.launch(JSWebAppLaunchConfigurationDelegate.java:96)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
    	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
    	at com.genuitec.eclipse.modernweb.common.core.server.internal.NodejsProjectServersManagerImpl$2.run(NodejsProjectServersManagerImpl.java:483)
    	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
    Caused by: java.io.IOException: Unrecognized respose: 500 Internal Server Error
    	at org.chromium.sdk.internal.wip.WipBackendImpl.queryWipBrowser(WipBackendImpl.java:186)
    	at org.chromium.sdk.internal.wip.WipBackendImpl.getTabs(WipBackendImpl.java:53)
    	at org.chromium.sdk.internal.wip.WipBrowserImpl.getTabs(WipBrowserImpl.java:33)
    	at com.genuitec.eclipse.javascript.debug.wip.core.launching.ChromeBrowserManager$1.selectTab(ChromeBrowserManager.java:198)
    	at org.chromium.debug.core.model.JavascriptVmEmbedderFactory$3.selectVm(JavascriptVmEmbedderFactory.java:77)
    	... 8 more
    
    #586705 Reply

    support-swapna
    Moderator

    Fedor,

    Thank you for the details. Yes, I am on the latest Chrome version.

    Couple of users recently reported similar problem with debugging due to bad hosts file.
    Can you please refer to this thread and check if the suggestion to clean up the hosts file helps fix the issue at your end? : https://www.genuitec.com/forums/topic/failed-to-get-tabs-for-debugging/

    If the above suggestion does not work, then please share with us the full log file by clicking on the ‘Export Log’ icon to help us investigate further. Also share with us the OS and version details.

    Please let us know how you get on with it.

    –Swapna
    Genuitec Support

    #586707 Reply

    Fedor Losev
    Participant

    Thanks a lot, indeed uncommenting localhost entry in hosts solved the issue, working now as expected.

    Though two old issues still make the feature limited (the main reason I use it rather rarely), I had hopes that these were fixed:
    – No angular –host parameter support, need to manually retype URL every launch
    – Console output is rudimentary and not so useful, no time, message type, coloring and, most important, locations with click to source navigation.

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Debug applicaton in Chrome does not work

You must be logged in to post in the forum log in