(fix) set memory baseline on MemoryCollector

[erikn69]

Fixes barryvdh/laravel-debugbar#1324
Fixes barryvdh/laravel-debugbar#1434

This pr allows only the memory peak to be shown with a baseline, this would normalize the differences in the presentation, currently the maximum peak of the process is shown, but only the memory used by the application should be shown

For example, in Windows a fresh app shows 20MB, while the same app in Linux only shows 3MB.
Added memory_reset_peak_usage for only check execution peaks

[barryvdh]

In the case of Laravel, wouldn't this discard the memory usage from the process up to the constructor of this class?

[erikn69]

Laravel, wouldn't this discard the memory usage from the process up to the constructor of this class?

Yes, before the service provider.
But still, it would only show the execution peaks within the script(the real app code)
any other solution? Should it be optional?

[barryvdh]

For the Octane problem, it would be enough to provide a method to reset for subsequent executions, but calling the memory_reset_peak_usage function might have unexpected results for other tools.

[erikn69]

Same app

WITH THIS PR:

Linux

Windows

---

WITHOUT THIS PR:

Linux

Windows

On windows memory goes up, the same app, also for mac

[barryvdh]

Yes but the actual process is using the highest variant, right?

[barryvdh]

I removed it from the constructor (for now). We can add it to the laravel-debugbar if Octane is running for example.

[erikn69]

the actual process is using the highest variant, right?

Without memory_reset_peak_usage yes, on the peak