View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000474 | Xdebug | Profiling | public | 2009-09-24 17:32 | 2020-03-12 16:47 |
| Reporter | jacobweber | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Product Version | 2.0.0dev | ||||
| Target Version | 2.6.0 | Fixed in Version | 2.6.0alpha1 | ||
| Summary | 0000474: Implement memory profiling | ||||
| Description | Any change we can get this patch folded into an Xdebug release? It seems to work for me. | ||||
| Tags | No tags attached. | ||||
| Operating System | |||||
| PHP Version | 5.3.0 | ||||
|
|
With minor changes working on 2.1.2 version and KCacheGrind. Original author "Benson, Geoff" as mentioned in link |
|
|
Added pull request on github. |
|
|
Even though the patch is correct, the results will not be. PHP's memory manager is quite unreliable for when it frees up memory. I don't quite know whether I want to add something that I know will confuse people... |
|
|
This helped me to see most memory used, optimize, etc. It actually doesn't matter for me to see correct numbers - when debugging memory usage all you need is allocations and percentage of total usage. |
|
|
I do agree with atis, memory is important even if the numbers are not correct. That's a feature I've been waiting for a few years now, a profiler without memory information is only half-complete. |