You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "David Li (Jira)" <ji...@apache.org> on 2022/07/06 13:38:00 UTC
[jira] [Resolved] (ARROW-15958) [Java][Docs] Document HistoricalLog for debugging
[ https://issues.apache.org/jira/browse/ARROW-15958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Li resolved ARROW-15958.
------------------------------
Fix Version/s: 9.0.0
Resolution: Fixed
Issue resolved by pull request 12656
[https://github.com/apache/arrow/pull/12656]
> [Java][Docs] Document HistoricalLog for debugging
> -------------------------------------------------
>
> Key: ARROW-15958
> URL: https://issues.apache.org/jira/browse/ARROW-15958
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Documentation, Java
> Reporter: David Li
> Assignee: David Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 9.0.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> {{BufferLedger}} has a {{HistoricalLog}} which records stack traces at various events in the buffer's life, such as when it was first allocated and upon incrementing/decrementing reference counts. While somewhat of an implementation detail, this information is useful for debugging, especially for tracking down memory leaks. We could document it (with a suitable warning).
> However, the stack trace is less useful than it first appears because it accidentally truncates the log. We should fix that too.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)