View Issue Details

IDProjectCategoryView StatusLast Update
0001450XdebugStep Debuggingpublic2018-01-29 21:50
Reportermartixy Assigned Toderick  
Status resolvedResolutionunable to reproduce 
Product Version2.5.4 
Summary0001450: Steps out of code / skips breakpoints
DescriptionWhile trying to bodge a simple templating engine, encountered a situation where at random points during the loop, it steps out of the function, skipping all breakpoints in the process.
Steps To ReproduceFunction(s), testcase and xdebug log in attached zip.
Additional InformationUsing phpStorm v2017.1.4(latest) with PHP 7.1.3(phpinfo)/7.1.6(cli) - frankly, no idea what's going on here. :)
TagsNo tags attached.
Operating SystemWindows 10 v1703
PHP Version7.1.5-7.1.9



2017-07-03 15:04

reporter (66,702 bytes)


2017-11-15 00:31

reporter   ~0004465

Last edited: 2017-11-15 00:34

+1 On this. This has been plaguing me for months. I turned on every kind of debug log file in the config (xdebug.txt, profiler_enable, auto_trace) and could not discern any reason for this. It just seemingly decides to randomly skip out of one or more functions on the stack for no reason. Though granted, xdebug liked completely hard crashing quite often when the latter debug file types were enabled. The longer I leave the debugger paused the more likely this is to happen. It seems about an 80% chance if I leave the debugger for more than 60 seconds without taking an action (stepping, evaluating, changing variables, etc). This has been killing me :-\

Running Windows 7 x64 w/ IntelliJ and currently php 7.1.2. IIRC I have encountered this with the latest php versions of both 7.0.x and 7.1.x for probably at least 4 months.


2017-12-17 14:34

administrator   ~0004517

Please provide a full example that I can run locally, and not just parts, and with a *matching* Xdebug remote log file. Without this, I can't investigate this, and hence not fix it.


2017-12-17 21:30

reporter   ~0004521

Hopefully martixy can beat me to it, but it will be a few weeks until I can supply the info you asked for.


2017-12-20 23:57

reporter   ~0004524

That IS a full example. You do see the attached zip right?


2018-01-01 20:50

administrator   ~0004537

Yes, I saw the attached zip. But I can't run any of that as it's not complete, *and* the remote_log file does not exactly match the provided file. I need a *full* (but small) reproducible case as is described at


2018-01-29 21:50

administrator   ~0004585

Can't reproduce this, and no feedback provided.

Issue History

Date Modified Username Field Change
2017-07-03 15:04 martixy New Issue
2017-07-03 15:04 martixy File Added:
2017-11-15 00:31 dakusan Note Added: 0004465
2017-11-15 00:34 dakusan Note Edited: 0004465
2017-12-17 14:34 derick Note Added: 0004517
2017-12-17 14:34 derick Assigned To => derick
2017-12-17 14:34 derick Status new => feedback
2017-12-17 21:30 dakusan Note Added: 0004521
2017-12-20 23:57 martixy Note Added: 0004524
2017-12-20 23:57 martixy Status feedback => assigned
2018-01-01 20:50 derick Note Added: 0004537
2018-01-01 20:50 derick Status assigned => feedback
2018-01-29 21:50 derick Note Added: 0004585
2018-01-29 21:50 derick Status feedback => resolved
2018-01-29 21:50 derick Resolution open => unable to reproduce
2020-03-12 16:33 derick Category Remote Debugging => Step Debugging