[ARROW-14302] [C++] Valgrind errors

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.0.0
• Component/s: C++
• Labels: query-engine
• External issue URL: https://github.com/apache/arrow/issues/29876
• Assignee: Michal Nowakiewicz
• Reporter: Jonathan Keane
• Created: 12/Oct/21 19:10
• Updated: 11/Jan/23 08:39
• Resolved: 19/Oct/21 11:46

Description

Separated from ARROW-14211

See nightly builds:
https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=12564&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181
https://github.com/ursacomputing/crossbow/runs/3780500627

Might this also be causing the R-valgrind errors too? https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=12612&view=results

==3189==   total heap usage: 5,735,451 allocs, 5,670,052 frees, 3,803,148,548 bytes allocated
==3189== 
==3189== LEAK SUMMARY:
==3189==    definitely lost: 0 bytes in 0 blocks
==3189==    indirectly lost: 0 bytes in 0 blocks
==3189==      possibly lost: 0 bytes in 0 blocks
==3189==    still reachable: 335,471,438 bytes in 65,399 blocks
==3189==                       of which reachable via heuristic:
==3189==                         newarray           : 4,264 bytes in 1 blocks
==3189==         suppressed: 0 bytes in 0 blocks
==3189== Reachable blocks (those to which a pointer was found) are not shown.
==3189== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==3189== 
==3189== For lists of detected and suppressed errors, rerun with: -s
==3189== ERROR SUMMARY: 172 errors from 1 contexts (suppressed: 0 from 0)
Found Valgrind errors
1
Error: `docker-compose --file /home/vsts/work/1/s/arrow/docker-compose.yml run --rm -e SETUPTOOLS_SCM_PRETEND_VERSION=6.0.0.dev373 ubuntu-r-valgrind` exited with a non-zero exit code 1, see the process log above.