andygrove opened a new pull request, #1426: URL: https://github.com/apache/arrow-java/pull/1426
## What's Changed `TestEmptyArrowBuf.testEmptyArrowBuf` wrapped the address of Netty's empty buffer, an 8-byte native allocation, in a 1024-byte `ArrowBuf` and wrote 10 bytes through it. The test now backs the no-op buffer with 1024 bytes from its own allocator, so it writes only memory it owns. The assertions are unchanged. This overrun causes the intermittent "Error occurred in starting fork" failure of `arrow-memory-netty` in the Windows CI job. #238 has the analysis. Before this change, `testEmptyArrowBuf` fails on macOS when a `malloc` interposer ends 8-byte allocations at a guard page. With it, the whole `memory-netty` suite passes under the same interposer and normally. One green Windows run would not prove much, because the failure hit about 7% of runs. Closes #238. -- 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]
