PHPStorm 9 is being hit by non-stop Xdebug requests when I do not have the listener enabled in PHPStorm and I don't have it enabled in the browser Chrome extension.
These windows constantly pop-up disrupting my ability to use the IDE:
This started after I had to disable xdebug.remote_autostart setting due to conflicts causing PHP scripts run at the CLI level to hang.
Now every background queue that executes is triggering this incoming connection message.
Every time I delete the server *.dev from PHPStorm it shows back up again.
How do I stop this?
Below is the full value list from the Debugger console when these undesired requests come in:
Related
I've had Xdebug set up and working properly in the past, but seem to have a real problem getting it to work consistently. This is a WordPress/WooCommerce install and I'm simply trying to load the homepage with some search query parameters so that I can debug a custom function.
Currently, I can't get it to break properly when I debug using a run configuration. It just won't break at all unless I tick the button to listen for incoming connections. At that point, I have to wade through every single index.php and cron.php process that runs, waiting for the right one to come along.
I'm not crazy, am I? I should be able to look at the single debug process and not all these others? It's as if PhpStorm is not receiving the initial connection when I run the configuration.
I'm trying to debug code that is on remote server.
I'm using
Ubuntu 16 server, LEMP, PHP 7.0 as remote server
OSX, PhpStorm, Chrome Xdebug helper as local environment
So, when
Xdebug connection is established by
ssh -R 9000:localhost:9000 {username}#{serverhost}
Xdebug helper in debug mode
PhpStorm start listening is enabled
Xdebug triggers to each requests not only from my browser or PhpStorm, but from all other users from the internet.
Is it normal?
Is it possible to watch only requests initiated from my PhpStorm or from my Chrome requests? If yes, so how to setup?
Xdebug triggers to each requests not only from my browser or PhpStorm, but from all other users from the internet.
Is it normal?
That depends on your Xdebug configuration. Right now it looks like it's configured to automatically attempt to debug every single request (not a good idea in many situations).
Is it possible to watch only requests initiated from my PhpStorm or from my Chrome requests? If yes, so how to setup?
Yes, make sure that xdebug.remote_autostart is turned off (set to 0/no).
Then just follow the official guide: https://www.jetbrains.com/help/phpstorm/debugging-with-phpstorm-ultimate-guide.html
Xdebug will see your Xdebug cookie set by Chrome Xdebug Helper (or GET/POST parameter if you pass it manually in URL/request) and will try to debug only those requests.
P.S. There is another scenarios where the aforementioned option will not help.. but so far it does not look like you are having that case (would need to see much more details for that).
Normal js code (no service worker, but the app has a manifest with an empty service worker).
A simple timeout to an ajax call that's the code.
I close all chrome tabs, I close the process in task manager, no more chrome processes and yet I still get requests on my server. This happens locally and on the server, I know this because I can see the cookies sent and for which user id is needed.
Also I know that chrome is running the code because there is a date in the request and is updated as it go.
Triple checked that chrome is closed on all users and all processed in task manager.
Is not a coincidence because at this moment I have 2 different users (different chrome profiles) doing this. Also in my dev server there are a lot of users with the same behaviour.
I'm also not sure is chrome, but has to be, node.js alone can't change the time of the request.
Win 10 and Chrome Version 60.0.3112.90 (Official Build) (64-bit)
Terrible and I don't know what to do...
if I restart my node.js server all the requests stops.
Was my mistake! As I have server side rendering (with react) I forgot that the timeout was also run on the server side. The fix was to don't run any timeouts on the server side.
Thanks anyway for the answers. I was concerned how chrome was still running my js code even shut down, made no sense at all!
I have developed a Google Extension for which I created a Windows installer package. That installer writes the corresponding registry entries as explained in https://developer.chrome.com/extensions/external_extensions#registry
All that works well in some computers. So, after I run the installer package and then run Google Chrome, a little popup appears telling me to enable the extension. I answer “Yes” to that question and from that time on, the extension works as expected.
However, in some computers, with the same version of Chrome (53.0.2785.116 m), the installer writes the corresponding entries to the registry but when I run Chrome, nothing happens and the extension is not listed in the chrome://extensions/ page.
In such cases, I can connect to web store to install the extension manually. However, this extension launches an application because it implements Native Messaging. When I install the extension manually it works (the native messaging host application is launched and works) but when I close and re-open Chrome, the host application is not run. To run it, I need to manually disable and then re-enable the extension.
Very strange what happening. Can you help me on this please?
Based from this thread, (which is somewhat related to your issue), when you close the Chrome, it will fire onDisconnect event that's why the application is not running.
Native messaging means only Chrome can start a host instance when it "connects". It's a misnomer, since connect() means "launch a new copy and talk to it".
There is no way to "attach" to an already-running process. If you close the host, stdio pipe is broken the Port object fires onDisconnect event. Then you need to re-launch the host from the extension to be able to talk to it.
You can check on this link. Just make sure that no antivirus or firewall programs on your computer are causing the problem. If you can open Google Chrome when the firewall is off, you may need to create an exception in your antivirus or firewall settings.
However, in some computers, with the same version of Chrome (53.0.2785.116 m), the installer writes the corresponding entries to the registry but when I run Chrome, nothing happens and the extension is not listed in the chrome://extensions/ page.
You may be encountering blacklisting if that extension was ever installed, then uninstalled.
What if the user uninstalls the extension?
If the user uninstalls the extension through the UI, it will no longer
be installed or updated on each startup. In other words, the external
extension is blacklisted.
How do I get off the blacklist?
If the user uninstalls your extension, you should respect that
decision. However, if you (the developer) accidentally uninstalled
your extension through the UI, you can remove the blacklist tag by
installing the extension normally through the UI, and then
uninstalling it.
I'm new to PhpStorm. I tried to use debugging for debuggin a Webpage and I configured it
After starting the debugger, it works for 40 seconds and then I get on the browser "500 Internal Server Error"
At this question Xdebug interrupts the running of PHP script they suggested to clear the watches. But in my Debugger there are no watches.
I use the PhpStorm with Ubuntu 14.04 and the web page is running on Apache
I used Eclipse before and I did not had this problem with XDebug.
Do someone has an idea?
Thanks to user LazeOne (who added a comment) I found the solution.
I added to my apache configuration (/etc/apache2/apache2.conf) the following line
FcgidIOTimeout 600 # for 10 minutes
and the debugger does not interrupt for the next 10 minutes