[ 
https://issues.apache.org/jira/browse/IMPALA-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe McDonnell resolved IMPALA-10285.
------------------------------------
    Fix Version/s: Not Applicable
       Resolution: Cannot Reproduce

> Impalad crashes with SIGSEGV in tcmalloc
> ----------------------------------------
>
>                 Key: IMPALA-10285
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10285
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 4.0
>            Reporter: Joe McDonnell
>            Priority: Blocker
>              Labels: broken-build, flaky
>             Fix For: Not Applicable
>
>
> An exhaustive debug run hit an Impalad SIGSEGV crash with the following stack:
> {noformat}
> Crash reason:  SIGSEGV
> Crash address: 0x2a
> Process uptime: not available
> Thread 406 (crashed)
>  0  impalad!tcmalloc::CentralFreeList::FetchFromOneSpans(int, void**, void**) 
> + 0x3b
>  1  impalad!tcmalloc::CentralFreeList::FetchFromOneSpansSafe(int, void**, 
> void**) + 0x1c
>  2  impalad!tcmalloc::CentralFreeList::RemoveRange(void**, void**, int) + 0xaf
>  3  impalad!tcmalloc::ThreadCache::FetchFromCentralCache(unsigned long, 
> unsigned long) + 0x5d
>  4  impalad!tc_newarray + 0x25b
>  5  libstdc++.so.6.0.24 + 0x11f5cd
>  6  libstdc++.so.6.0.24 + 0x112e0b
>  7  libstdc++.so.6.0.24 + 0x11db89
>  8  libstdc++.so.6.0.24 + 0x102bd3
>  9  libstdc++.so.6.0.24 + 0x1029e9
> 10  libstdc++.so.6.0.24 + 0x102b05
> 11  libstdc++.so.6.0.24 + 0x10e3b5
> 12  impalad!impala::PrintId(impala::TUniqueId const&, 
> std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> 
> > const&) [debug-util.cc : 109 + 0x19]
> {noformat}
> This is a classic memory corruption symptom. Since memory corruptions can 
> have lots of different symptoms, IMPALA-10276 may be related. SinceĀ 
> query_test/test_scanners_fuzz.py:82: in test_fuzz_alltypes() is one of the 
> failing tests, IMPALA-10267 may be related as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to