Editor is not responding

[johnish]

When I use php-debug on my Mac with Xdebug I will get an message that says "Editor is not responding". This does not happen every time. Choosing to wait does not ever bring functionality back to atom. It is still in a hung/frozen state. The only option that works is to close the editor.

OS X El Capitan 10.11.6 Atom 1.18.0 x64 php-debug 0.2.4 php 5.5.35 Xdebug v2.2.3 Xdebug Info: Supported protocols Revision DBGp - Common DeBuGger Protocol $Revision: 1.145 $

Directive Local Value Master Value xdebug.auto_trace Off Off xdebug.cli_color 0 0 xdebug.collect_assignments Off Off xdebug.collect_includes On On xdebug.collect_params 0 0 xdebug.collect_return Off Off xdebug.collect_vars Off Off xdebug.coverage_enable On On xdebug.default_enable On On xdebug.dump.COOKIE no value no value xdebug.dump.ENV no value no value xdebug.dump.FILES no value no value xdebug.dump.GET no value no value xdebug.dump.POST no value no value xdebug.dump.REQUEST no value no value xdebug.dump.SERVER no value no value xdebug.dump.SESSION no value no value xdebug.dump_globals On On xdebug.dump_once On On xdebug.dump_undefined Off Off xdebug.extended_info On On xdebug.file_link_format no value no value xdebug.idekey no value no value xdebug.max_nesting_level 100 100 xdebug.overload_var_dump On On xdebug.profiler_aggregate Off Off xdebug.profiler_append Off Off xdebug.profiler_enable Off Off xdebug.profiler_enable_trigger Off Off xdebug.profiler_output_dir /var/tmp/ /var/tmp/ xdebug.profiler_output_name cachegrind.out.%p cachegrind.out.%p xdebug.remote_autostart On On xdebug.remote_connect_back On On xdebug.remote_cookie_expire_time 3600 3600 xdebug.remote_enable On On xdebug.remote_handler dbgp dbgp xdebug.remote_host 127.0.0.1 127.0.0.1 xdebug.remote_log no value no value xdebug.remote_mode req req xdebug.remote_port 9000 9000 xdebug.scream Off Off xdebug.show_exception_trace Off Off xdebug.show_local_vars Off Off xdebug.show_mem_delta Off Off xdebug.trace_enable_trigger Off Off xdebug.trace_format 0 0 xdebug.trace_options 0 0 xdebug.trace_output_dir /var/tmp/ /var/tmp/ xdebug.trace_output_name trace.%c trace.%c xdebug.var_display_max_children 128 128 xdebug.var_display_max_data 10000 10000 xdebug.var_display_max_depth 20 20

[cchamplin]

I unfortunately do not have a mac to test this with. Is there anyone else who can confirm this is an issue on macs?

[pelallemant]

I've a similar problem on Linux Ubuntu. When I toogle the debugger window, the application is "freezing". It seems it is listening for the script to be launched, and doesn't give back the hand on atom ( version 1.18.0 ). I had to close the atom window.

[JonMadVal]

Same issue here running Atom 1.20.2 x64 and PHP 7.1 in Linux Fedora 23, when i run the app and the debugger, this get froze Atom and i can't get back. the only solution is close de atom's window.

[jeffreyducharme]

This is also happening to me. Stops me from moving to Atom

[cchamplin]

Ok I think I have been able to reproduce this, with the changes in the last release there was a situation in which if the socket failed to bind it would basically retry binding forever, this should be patched up in 0.2.6

[cchamplin]

0.2.6 as landed, can a few of you let me know if your issues are resolved?

[bkmeneguello]

I'm still having this issue. Whenever the PHP Debugger panel is open in short time the UI becomes frozen. How can I send more useful details? My env: Atom : 1.23.3 Electron: 1.6.15 Chrome : 56.0.2924.87 Node : 7.4.0 PHP Debug: 0.2.6 PHP: 7.0.22-0ubuntu0.16.04.1 (cli) ( NTS ) Xdebug: v2.4.0

[bkmeneguello]

I've bissected the problem disabling some extensions and detected that the problem occurs whenever the package (atom-autocomplete-php)[https://atom.io/packages/atom-autocomplete-php] is enabled. When the (autocomplete-php)[https://atom.io/packages/autocomplete-php] is active (exclusively) the problems doesn't occur.

[StAmourD]

@bkmeneguello Thank you!

I started having the same problem a couple days ago. As soon as I would click PHP Debug to start the debugger, the UI would freeze then Atom would crash. Disabling https://atom.io/packages/atom-autocomplete-php as you suggested allows PHP-Debug to start as expected.