NVIDIA / NVIDIA/cudf

[BUG] Uninitialized read detected in parquet chunked reader/writer

Open
#19,247 9 comments 0 reactions 1 assignee Assigned to @vuule View on GitHub
bug cuIO
Dominant language
C++
Stars
9.8k
Forks
1.1k
Avg merge
3d 6m
Merged PRs (30d)
278

Description

While debugging using `compute-sanitizer` with `initcheck`, I found the following issue:
```
========= Host API memory access error at host access to 0x7e537afa8200 of size 347,392 bytes
========= Uninitialized access at 0x7e537afa8e40 on access by cudaMemcpy source
========= Saved host backtrace up to driver entry point at error
========= Host Frame: cudaMemcpyAsync_ptsz [0x1e5ce0] in PARQUET_TEST
========= Host Frame: cudf::detail::cuda_memcpy_async_impl(void*, void const*, unsigned long, cudf::detail::host_memory_kind, rmm::cuda_stream_view) [0x73d002] in PARQUET_TEST
========= Host Frame: cudf::detail::host_vector cudf::detail::make_host_vector_async(cudf::device_span, rmm::cuda_stream_view) [0x498aa5] in PARQUET_TEST
========= Host Frame: cudf::io::parquet::detail::include_decompression_scratch_size(cudf::device_span, cudf::device_span, cudf::device_span, rmm::cuda_stream_view) [0x494a6f] in PARQUET_TEST
========= Host Frame: cudf::io::parquet::detail::reader::impl::setup_next_subpass(cudf::io::parquet::detail::reader::impl::read_mode) [0x48423e] in PARQUET_TEST
========= Host Frame: cudf::io::parquet::detail::reader::impl::read_chunk() [0x479107] in PARQUET_TEST
========= Host Frame: cudf::io::parquet::detail::chunked_reader::read_chunk() const [0x47107d] in PARQUET_TEST
========= Host Frame: cudf::io::chunked_parquet_reader::read_chunk() const [0x3d92af] in PARQUET_TEST
========= Host Frame: (anonymous namespace)::chunked_read(unsigned long, unsigned long) [0x195719] in PARQUET_TEST
========= Host Frame: ParquetChunkedReaderTest_TestChunkedReadNoData_Test::TestBody() [0x1964e0] in PARQUET_TEST
========= Host Frame: void testing::internal::HandleExceptionsInMethodIfSupported(testing::Test*, void (testing::Test::*)(), char const*) [0x25c3bc] in PARQUET_TEST
========= Host Frame: testing::Test::Run() [0x23f26d] in PARQUET_TEST
========= Host Frame: testing::TestInfo::Run() [0x23f3f4] in PARQUET_TEST
========= Host Frame: testing::TestSuite::Run() [0x23f576] in PARQUET_TEST
========= Host Frame: testing::internal::UnitTestImpl::RunAllTests() [0x252d8e] in PARQUET_TEST
========= Host Frame: testing::UnitTest::Run() [0x23f724] in PARQUET_TEST
========= Host Frame: main [0xa8c5d] in PARQUET_TEST
```

While this does not cause any obvious issue so far, this is an indication of a potential bug that we need to fix.

Unfortunately I don't have a debug build thus cannot have a better stacktrace for this.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.