You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "hermanschaaf (via GitHub)" <gi...@apache.org> on 2023/04/18 16:19:38 UTC
[GitHub] [arrow] hermanschaaf opened a new issue, #35212: [Go] Add more frames to Checked Allocator memory leak output
hermanschaaf opened a new issue, #35212:
URL: https://github.com/apache/arrow/issues/35212
### Describe the enhancement requested
The `CheckedAllocator` output right now provides a single line of context, roughly indicating which type was involved. This is fine for testing within Arrow itself, but in large applications this is often not enough to narrow down where a memory leak is coming from. It would be very helpful if the full call stack could be provided in the output.
### Component(s)
Go
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] zeroshade closed issue #35212: [Go] Add more frames to Checked Allocator memory leak output
Posted by "zeroshade (via GitHub)" <gi...@apache.org>.
zeroshade closed issue #35212: [Go] Add more frames to Checked Allocator memory leak output
URL: https://github.com/apache/arrow/issues/35212
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] hermanschaaf commented on issue #35212: [Go] Add more frames to Checked Allocator memory leak output
Posted by "hermanschaaf (via GitHub)" <gi...@apache.org>.
hermanschaaf commented on issue #35212:
URL: https://github.com/apache/arrow/issues/35212#issuecomment-1513480492
I have an implementation of this (and it's been very useful) but not sure how we'd want the details to look. I might open a draft PR for feedback soon
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow] zeroshade commented on issue #35212: [Go] Add more frames to Checked Allocator memory leak output
Posted by "zeroshade (via GitHub)" <gi...@apache.org>.
zeroshade commented on issue #35212:
URL: https://github.com/apache/arrow/issues/35212#issuecomment-1513491630
Sounds good @hermanschaaf I'd be happy to look at it when you submit the draft PR. If it doesn't automatically add me to it just tag me on it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org