-
-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Optional memory profiler #32959
Comments
No description provided. |
An optional memory profiler, which goes in tandem with the optional Applying both patches gives for me (screen dump): ~> patch -p1 < ../obmalloc-patch
This patch:
The patch *can* be applied without the object allocator and it *does* Needs docs & tests :( The interface can be improved (just like everything I am submitting this for testing, reviewing, comments and more ideas. Comments welcome. As usual, flames to /dev/null <wink>. Status set straight to Postponed. Assigned to marangoz who's in charge of |
Logged In: YES The patch, in its current form, fails to apply (4 hunks http://mail.python.org/pipermail/python-dev/2000-August/008527.html I recommend to reject this patch, since I cannot see what |
Logged In: YES I had the impression that the feature was useful, but |
Logged In: YES I still recommend to reject this patch. |
Logged In: YES I'm closing this patch now. I believe the statistics |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: