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/02/05 18:06:00 UTC
[jira] [Commented] (ARROW-14478) [C++] Potential stack overflow in async scanner
[ https://issues.apache.org/jira/browse/ARROW-14478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487533#comment-17487533 ]
David Li commented on ARROW-14478:
----------------------------------
A similar issue:
{noformat}
[----------] 18 tests from TestScan/TestIpcFileFormatScan
[ RUN ] TestScan/TestIpcFileFormatScan.ScanRecordBatchReader/0Threaded16b1024r
[ OK ] TestScan/TestIpcFileFormatScan.ScanRecordBatchReader/0Threaded16b1024r (58 ms)
[ RUN ] TestScan/TestIpcFileFormatScan.ScanRecordBatchReader/1Serial16b1024r
[ OK ] TestScan/TestIpcFileFormatScan.ScanRecordBatchReader/1Serial16b1024r (6 ms)
[ RUN ] TestScan/TestIpcFileFormatScan.ScanBatchSize/0Threaded16b1024r
unknown file: error: SEH exception with code 0xc00000fd thrown in the test body.
[ FAILED ] TestScan/TestIpcFileFormatScan.ScanBatchSize/0Threaded16b1024r, where GetParam() = Threaded16b1024r (205 ms) {noformat}
> [C++] Potential stack overflow in async scanner
> -----------------------------------------------
>
> Key: ARROW-14478
> URL: https://issues.apache.org/jira/browse/ARROW-14478
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Reporter: David Li
> Priority: Major
> Labels: dataset, query-engine
>
> Observed in [AppVeyor CI|https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/41288964/job/6s4bx6cd2kc6eld6] on the main branch:
> {noformat}
> [ RUN ] TestScan/TestCsvFileFormatScan.ScanBatchSize/0AsyncThreaded16b1024r
> unknown file: error: SEH exception with code 0xc00000fd thrown in the test body.
> [ FAILED ] TestScan/TestCsvFileFormatScan.ScanBatchSize/0AsyncThreaded16b1024r, where GetParam() = AsyncThreaded16b1024r (250 ms){noformat}
> From some searching, this code corresponds to a stack overflow. We've previously seen errors similar to this, so it might be good to identify and track this down too. (It seems less likely on Linux due to the larger default stack size.)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)