Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an usage example at https://github.com/PHPOffice/PhpSpreadsheet/issues/3814 #392

Merged
merged 1 commit into from
Dec 22, 2023
Merged

Add an usage example at https://github.com/PHPOffice/PhpSpreadsheet/issues/3814 #392

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/memory-profiler.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -437,6 +437,7 @@ system("sudo reli i:m -p {$pid} --no-stop-process >{$pid}_memory_analyzed.json")
And you can also use [Xdebug](https://xdebug.org/). If the target is stopped at one of the breakpoints you set, then it's a good timing to analyze the target by Reli. This way you don't have to change the target code, though the behavior of the PHP VM isn't exactly same as the production enviornment in this case. Xdebug itself can be used to get the content of variables, but if you use Reli in addition to it, you can also get the statical data of the memory usage or reference graphs.

## Examples of diagnosing memory issues in the wild
- https://github.com/PHPOffice/PhpSpreadsheet/issues/3814#issuecomment-1862367771
- https://github.com/smalot/pdfparser/issues/631#issuecomment-1847772214

## More detailed explanation of the output
Expand Down
Loading