You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I often find it useful to run debugging / trace capture / profiling only for the next request. Keeping trace / profile enabled for batch of requests (even if they're triggered by single browser navigation request) is problematic for following reasons:
it produces multiple trace / profile files which may take necessary disk space,
multiple generated files make it harder to find the actual trace / profile file of interest,
it puts additional load on the server,
it may lead to temporary depletion of available request handlers on the server, causing 5xx error codes (for example a page with dozens of AJAX calls, web server set up to pass handling of 404's to PHP etc.)
Ideally, there should be a checkbox / keyboard shortcut which would allow users to enable XDebug only for the next request (and the next request only, following requests executed due to loading of the request should not have XDebug enabled)
The text was updated successfully, but these errors were encountered:
I often find it useful to run debugging / trace capture / profiling only for the next request. Keeping trace / profile enabled for batch of requests (even if they're triggered by single browser navigation request) is problematic for following reasons:
Ideally, there should be a checkbox / keyboard shortcut which would allow users to enable XDebug only for the next request (and the next request only, following requests executed due to loading of the request should not have XDebug enabled)
The text was updated successfully, but these errors were encountered: