paleolimbot opened a new issue, #1211:
URL: https://github.com/apache/arrow-adbc/issues/1211
From the extended R checks added in #1210.
```
==6428== 4,104 bytes in 1 blocks are possibly lost in loss record 679 of
2,839
==6428== at 0x4848899: malloc (in
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==6428== by 0x204315EA: ??? (in
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6)
==6428== by 0x20435899: sqlite3Malloc (in
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6)
==6428== by 0x20447773: ??? (in
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6)
==6428== by 0x203CA147: ??? (in
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6)
==6428== by 0x20478E8F: sqlite3VdbeExec (in
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6)
==6428== by 0x2048781E: sqlite3_step (in
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6)
==6428== by 0x2037842F: SqliteStatementInitIngest (sqlite.c:1232)
==6428== by 0x2037865D: SqliteStatementExecuteIngest (sqlite.c:1273)
==6428== by 0x2037885C: SqliteStatementExecuteQuery (sqlite.c:1316)
==6428== by 0x1EF468F8: RAdbcStatementExecuteQuery (radbc.cc:515)
==6428== by 0x495C96D: R_doDotCall (dotcode.c:874)
```
These tests run on CRAN and I don't see a valgrind error there, so perhaps
this can be fixed by forcing use of the vendored SQLite (which is probably a
much newer version than that packaged with Ubuntu).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
