WebStorm debug run another instance of Chrome instead of currently running one Follow
WebStorm debug run another instance of Chrome instead of currently running one.
When I run, it will run on Chrome that currently running, the one with my settings and plugins (And also Jetbrain IDE Support)
but when i click debug, it will pop up another instance of Chrome, which have none of my settings and plugins, it look like fresh installed Chrome
It start to be like this since I update from WebStorm 2017.1 to 2017.3
How can I fix it?
P.S. sorry for my English, It's not my native language
Please sign in to leave a comment.
Since 2017.3, Chrome extension is not used for debugging by default - see https://blog.jetbrains.com/webstorm/2017/10/webstorm-2017-3-eap-173-3415/,. Chrome protocol with
--remote-debugging-portoption is used instead. Debugging session is started in a new window and using custom profile because it's required to run chrome with
--remote-debugging-portargument, and a port for debugging can't be opened after browser is started.
If you like to debug with extension, as before, please enable Update application in Chrome in Preferences | Build, Execution, Deployment | Debugger | Live Edit
Thank you so much :)
I enabled Update application in Chrome and it still opens a new Chrome window. What else can it be?
I figured it out. My VPN Extenion was active. Once I turned off the VPN all was good.
This might be a different issue. But my phpstorm is opening Chrome without any of my chrome extensions and with me not logged into Google. I thought it might be that phpstorm is opening chrome as root, but the activity monitor shows a second Google Chrome process with my regular user.
Please see my answer above - https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000781870/comments/115000638530
For me the best solution was to allow PHPStorm to continue to use it's own profile and simply synchronise my settings. I only had to login to google to pull down all my extensions anyway.
I was able to configure PHPStorm to launch Chrome using my main profile, but I couldn't start a debugging session without closing all chrome windows and exiting the application first. Not workable if you already have a bunch of other windows open for other purposes.
>I was able to configure PHPStorm to launch Chrome using my main profile, but I couldn't start a debugging session without closing all chrome windows and exiting the application first
"To open a new Chrome instance with your familiar look-and-feel, configure Chrome in WebStorm to start with your
chrome-user-data. In this case, before starting a debugging session, always make sure that Chrome is not already running with your
chrome-user-data. Otherwise WebStorm still launches another instance of Chrome with your
chrome-user-databut is unable to open a debugging port for it."
If you like to be able to attach a debugger to a running Chrome instance, you need using JetBrains Chrome extension - see instructions on activatuing it in https://www.jetbrains.com/help/webstorm/live-editing.html
There is no Live Edit in 2019.1 of PHPstorm
@MiklaDfar You need installing Live Edit plugin from Settings | Plugins; see https://www.jetbrains.com/help/phpstorm/2019.1/live-editing.html#ws_js_live_edit_before_you_start
I installed Live Edit and I get the debug session opened in the currently opened browser, which is great.
Any particular preference on using the new approach of spawning a new browser instance with the custom profile? I honestly only need the live edit workflow to simplify the back and forth between IDE and browser with the app switcher, alongside with other browser tabs that might have docs, references, etc. Believe it or not having the same browser icon listed twice on the app switcher makes it a common mistake to switch to the wrong instance
I am using:
I followed the `Live Edit` instruction mentioned in this thread, but still it opens a new chrome window without my chrome profile being active. Any solution?
Instructions above are outdated, as the JetBrains IDE Chrome extension is deprecated and not suppirted anymore.
There is currently no way to attach a debugger to a running Chrome instance, because the IDE uses Chrome protocol with
But, if you do this, always make sure that Chrome is not already running with your user data before starting a debugging session, it won't work otherwise.
Is there any ideas to fix it? Such as chrome extension?
sorry, could you clarify what you'd like to be fixed?
I mean open url in openning browser. I know it's base on chrome security policy, but still hope to get some idea.