The site works on Apache 2.2.22 PHP 5.3.13 xdebug 2.2.0

Php.ini configs

zend_extension = "c:/wamp/bin/php/php5.3.13/zend_ext/php_xdebug-2.2.0-5.3-vc9.dll" [xdebug] xdebug.remote_enable = On xdebug.profiler_enable = off xdebug.profiler_enable_trigger = off xdebug.profiler_output_name = cachegrind.out.%t.%p xdebug.profiler_output_dir = "c:/wamp/tmp" xdebug.remote_handler = "dbgp" xdebug.remote_host = "127.0.0.1" xdebug.trace_output_dir = "C:\xampp\tmp" xdebug.remote_autostart=on xdebug.remote_connect_back=on xdebug.remote_port=9001 xdebug.remote_mode=req xdebug.idekey="PHPSTORM"

Everything worked fine until I started working with a file of 4498 lines. When it comes to this file, the site falls off with a white screen.

Tell me how this can be eliminated.

    2 answers 2

    Turn on the log and see what happens:

     xdebug.remote_log="/path/to/file"

    Most likely xdebug falls in segfault. Try to disable autostart, let it work only if there are balls in the file.

    • In segfault xdebug does not fall. Problems arise during debug on Drupal. Special patterns of the fall is not observed. - Pavel Zhukov

    Increased memory contrary to warnings - it worked as a watch

     ; Maximum amount of memory a script may consume (128MB) ; http://php.net/memory-limit memory_limit = 300M