Problem Debugging WebStorm in Chrome

I am unable to debug at al in Chrome. I set it as my default broswer but when I try to debug, I see Connecting to 127.0.0.1:7930 in the Debugger window, but nothing happens (Chrome doesn't popup or anything). I have no idea how to trouble shoot this....any ideas?
BTW my chrome is latest: 14.0.835.163

I really hope someone from JetBrains support answers this , because  there is virtually NO support on the internet for debugging from  WebStorm......thanks!
-Mike

16 comments
Comment actions Permalink

Please click on Help | 'Reveal Log' item and attach 'idea.log' file from the opened directory.

0
Comment actions Permalink

Here is yhe log....



Attachment(s):
idea.log.zip
0
Comment actions Permalink

Are there detailed instructions somewhere on how to connect WebStorm on MAC OSX to Chrome (including xdebug configuaration)?  I think part of the probelm here is that I'm missing a step...

0
Comment actions Permalink

xDebug (the server-side PHP code debugger) totally unrelated to javascript debugging in Chrome discussed here.

What are you trying to debug? JS or PHP?

0
Comment actions Permalink

Javascript. Am I able to debug javasscript from WebStorm's IDE? If so where can I find a step by step tutorial on how to connect MY Webstorm HTML, CSS & Javascript based project to Google Chrome in DEBUG mode??

regards

-Mike

0
Comment actions Permalink

We have some tutorials about JavaScript debugging in our wiki: for local debugging (when files from local folders are opened in browser) see http://wiki.jetbrains.net/intellij/Debugging_JavaScript_locally_in_Firefox_with_WebStorm_and_PhpStorm,
for remote debugging (when js files are loaded from a server) see http://wiki.jetbrains.net/intellij/Remote_JavaScript_debugging_with_WebStorm_and_PHPStorm#Starting_the_debugging_session.
These tutorials describe debugging in Firefox browser but debugging in Chrome isn't much different: it works via Chrome API so it doesn't require to install an extension.

0
Comment actions Permalink

Thanks for the documentation. However this does not help me troubleshoot my issues debugging with Chrome. When I try to debug with Chome, Webstorm seems to just show Connecting to 127.0.0.1:7930... and NOTHING happens. Can you please provide some troubleshooting steps or tip and what could be causing this issue.

regards

-Mike

0
Comment actions Permalink

Please try to close all running Chrome instances before starting the debugger. If it doesn't help open File | Settings | Web Browsers, click on 'Settings' button in 'Chrome' group and enable 'Use custom profile' and 'Enable remote debug' options.

0
Comment actions Permalink

If I understand you correctly you tried the suggested options and they didn't help you. So could you please enable additional logging by replacing <WebStorm_Home>/bin/log.xml file by the attached one, restart WebStorm, reproduce the problem and attach idea.log file?



Attachment(s):
log.xml
0
Comment actions Permalink

I run on MAC OS so My Webstorm 2.1.5 is located in /applications

Here is what I did:

1. Copied log.xml to /applications/bin
2. Started WebStorm
3. Started debug session
4. Uploaded resulting log file in to here

Are these steps correct?

I don't see where in the log webstorm is trying to connect to Chrome, but you have a look...


regards,

-Mike



Attachment(s):
idea.log.zip
0
Comment actions Permalink

You copied the log.xml to wrong place. Please click on WebStorm icon and select 'Show package contents' from the popup menu. After that WebStorm home folder should be opened in Finder. Then go into 'bin' folder, it should already contain log.xml file. Replace it by the provided file and start WebStorm.

0
Comment actions Permalink

Any resolution on this? I am experiencing this on Mac as well. I followed all the steps here, but no luck.

After switching out my log.xml file in the "Show package contents", below is what ended up in the idea.log file:

2011-11-28 16:00:11,501 [  21648]  DEBUG - tion.impl.ChromeConnectionImpl - Waiting for 127.0.0.1:7930
2011-11-28 16:00:11,503 [  21650]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:16,516 [  26663]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:21,527 [  31674]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:26,538 [  36685]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:31,551 [  41698]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:36,561 [  46708]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:41,575 [  51722]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:46,586 [  56733]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:51,598 [  61745]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:00:56,607 [  66754]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2011-11-28 16:01:01,618 [  71765]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet

0
Comment actions Permalink

I can confirm it is also happening on Windows. Please log this in as a bug for us if so?

0
Comment actions Permalink

I just started experiencing this today with WebStorm version 2.1.5 with a new version of Chrome that was pushed out today, 17.0.963.46 m.  It works ok in Webstorm version
3.0.2.  However, due to other issues in version 3.0.2 I want to revert back to version 2.1.5.

In version2.1.5:
Chrome is started but displays a page saying "
Waiting for connection from JetBrains WebStorm...
" and in the WebStorm Variables tab is says "
Connecting to 127.0.0.1:7930"
The log looks like:
2012-02-09 14:04:32,426 [1030869]  DEBUG - pl.ChromeConnectionManagerImpl - Creating new connection to Chrome
2012-02-09 14:04:42,955 [1041398]  DEBUG - tion.impl.ChromeConnectionImpl - New connection to 127.0.0.1:7930 initialized
2012-02-09 14:04:42,955 [1041398]  DEBUG - t.debugger.impl.JSDebugProcess - FileFinder: RemoteDebuggingFileFinder:
  http://localhost/TabletTest->file://D:/Projects/RiaTest
   
2012-02-09 14:04:42,970 [1041413]  DEBUG - tion.impl.ChromeConnectionImpl - Waiting for 127.0.0.1:7930
2012-02-09 14:04:43,890 [1042333]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2012-02-09 14:04:58,677 [1057120]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2012-02-09 14:05:14,726 [1073169]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
...

In version 3.0.2 the log looks like:
2012-02-09 15:16:02,004 [  48163]  DEBUG - pl.ChromeConnectionManagerImpl - Creating new connection to Chrome
2012-02-09 15:16:02,051 [  48210]  DEBUG - tion.impl.ChromeConnectionImpl - New connection to 127.0.0.1:7930 initialized
2012-02-09 15:16:02,067 [  48226]  DEBUG - t.debugger.impl.JSDebugProcess - FileFinder: RemoteDebuggingFileFinder:
  http://localhost/TabletTest->file://D:/Projects/RiaTest
   
2012-02-09 15:16:02,504 [  48663]  DEBUG - tion.impl.ChromeConnectionImpl - Launching Chrome: additional args=[--remote-debugging-port=7930]
2012-02-09 15:16:02,504 [  48663]  DEBUG - tion.impl.ChromeConnectionImpl - Waiting for 127.0.0.1:7930
2012-02-09 15:16:02,504 [  48663]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 isn't available yet
2012-02-09 15:16:03,504 [  49663]  DEBUG - pl.ChromeConnectionManagerImpl -  
java.net.BindException: Address already in use: JVM_Bind
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
    at java.net.ServerSocket.bind(ServerSocket.java:328)
    at java.net.ServerSocket.bind(ServerSocket.java:286)
    at com.intellij.chromeConnector.connection.impl.ChromeConnectionManagerImpl.canConnectToSocket(ChromeConnectionManagerImpl.java:98)
    at com.intellij.chromeConnector.connection.impl.ChromeConnectionManagerImpl.canConnectToSocket(ChromeConnectionManagerImpl.java:88)
    at com.intellij.chromeConnector.connection.impl.ChromeConnectionImpl.connectToChrome(ChromeConnectionImpl.java:122)
    at com.intellij.chromeConnector.connection.impl.ChromeConnectionImpl.connect(ChromeConnectionImpl.java:80)
    at com.intellij.chromeConnector.connection.impl.V8ConnectionImpl$1.run(V8ConnectionImpl.java:128)
    at com.intellij.openapi.application.impl.ApplicationImpl$6.run(ApplicationImpl.java:425)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    at com.intellij.openapi.application.impl.ApplicationImpl$1$1.run(ApplicationImpl.java:140)
2012-02-09 15:16:03,520 [  49679]  DEBUG - tion.impl.ChromeConnectionImpl - Socket 127.0.0.1:7930 is available
2012-02-09 15:16:03,520 [  49679]  DEBUG - pl.ChromeConnectionManagerImpl - Trying to connect to 7930
2012-02-09 15:16:03,567 [  49726]  DEBUG - tion.impl.ChromeConnectionImpl - findTab: 1 tabs
2012-02-09 15:16:03,567 [  49726]  DEBUG - tion.impl.ChromeConnectionImpl - tab url: file://C:/DOCUME~1/LASTRA~1/LOCALS~1/Temp/chrome6658041126442780842.html
2012-02-09 15:16:03,567 [  49726]  DEBUG - tion.impl.ChromeConnectionImpl - Tab found
2012-02-09 15:16:03,567 [  49726]  DEBUG - tion.impl.ChromeConnectionImpl - attaching to tab
2012-02-09 15:16:03,645 [  49804]  DEBUG - tion.impl.ChromeConnectionImpl - attached to tab
2012-02-09 15:16:03,723 [  49882]  DEBUG - ection.impl.ChromeProtocolUtil - change location evaluated
2012-02-09 15:16:03,738 [  49897]  DEBUG - tion.impl.ChromeConnectionImpl - Navigated to http://localhost/TabletTest/launch.html

0
Comment actions Permalink

Hi Lisa,

You have to use v3.0.2, I'm afraid, as previous versions do not support new Chrome debugging protocol.

See this ticket for details: http://youtrack.jetbrains.net/issue/IDEA-80119?projectKey=IDEA

0

Please sign in to leave a comment.