[
https://issues.apache.org/jira/browse/KUDU-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152269#comment-17152269
]
Grant Henke commented on KUDU-3030:
-----------------------------------
This was recently seen a few more times because tcmalloc heap sampling was
enabled by default in Kudu 1.10.0+:
https://github.com/apache/kudu/commit/3175ed07df9c9280adec08fea18d15acbd45a4dc
The workaround is to disable it by setting `--heap-sample-every-n-bytes=0`, but
we really need a fix or to disable heap sampling by default.
> Crash in tcmalloc stack unwinder
> --------------------------------
>
> Key: KUDU-3030
> URL: https://issues.apache.org/jira/browse/KUDU-3030
> Project: Kudu
> Issue Type: Bug
> Components: build
> Affects Versions: 1.11.0
> Reporter: Todd Lipcon
> Priority: Critical
>
> We recently saw a crash where the tcmalloc heap profiler was trying to unwind
> the stack, and ended up accessing invalid memory. The issue here is that
> tcmalloc is relying on frame pointers for heap unwinding, but this particular
> stack trace was going through libstdc++, which was installed on the system
> and doesn't have frame pointers. "usually" this works OK, but when we get
> unlucky, we can crash.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
