-
Notifications
You must be signed in to change notification settings - Fork 412
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.
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
Memory Support: read and display memory uage #174
Open
danielbeardsley
wants to merge
7
commits into
jokkedk:master
Choose a base branch
from
iFixit:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Easier to read / maintian this way.
Xdebug has supported memory for a while, but this tool hadn't been updated to use it. Here we add a new "costFormat" option of "bytes of memory". We pass this through to the pre-processor to have it read the memory cost field instead of the time cost field.
Just like the PHP pre-processor, we read the memory if costFormat == 'bytes'.
Some other pull upgraded jQuery and that caused this jQuery plugin to crash. Stubbing this "browser" object will allow expressions like "$.browser.ie" to return undefined instead of throwing.
Previously, the tablesorter was detecting numeric values with thousands separators as "text" and sorting them incorrectly. I added thousands separators for bytes values, so they are easier to read at a glance as the numbers get long but the sorter hadn't been parsing them well. Note: I'm not sure why the "Cost" column was set to "sorter: false" on the subtables, it had still been sorting but it had been falling back to auto-detecting the sort type.
Add Memory support
Can we get this merged @alpha0010 ? :) |
Wow... I had forgotten I did this. Thanks for commenting and reminding me. |
Unfortunately hard to find time when my work is on other projects, but I will try to handle this soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support retrieving and using the memory information that XDebug records.
Adding "memory" as cost format option was the easiest way to get it done.
This also adds the php 8.2 fixes in #169 (thanks @mmcev106)
Closes #51
Note: This went through a lot of CR and QA in our fork: iFixit#1