[
https://issues.apache.org/jira/browse/ARROW-16873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17557182#comment-17557182
]
Kouhei Sutou commented on ARROW-16873:
--------------------------------------
This may be related to ARROW-16717.
System memory pool wasn't system {{malloc()}} before ARROW-16717. jemalloc was
used since ARROW-16717.
It might change the behavior.
> [Python] test_debug_memory_pool_disabled segfaulting on MacOS CI
> ----------------------------------------------------------------
>
> Key: ARROW-16873
> URL: https://issues.apache.org/jira/browse/ARROW-16873
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Reporter: David Li
> Priority: Major
>
> Observed on master and many PRs, example:
> https://github.com/apache/arrow/runs/6991997196?check_suite_focus=true
> From a quick read, it's likely just that the stderr isn't necessarily empty
> as the test expects.
> {noformat}
> =================================== FAILURES
> ===================================
> _____________ test_debug_memory_pool_disabled[system_memory_pool]
> ______________
> pool_factory = <built-in function system_memory_pool>
> @pytest.mark.parametrize('pool_factory', supported_factories())
> def test_debug_memory_pool_disabled(pool_factory):
> res = run_debug_memory_pool(pool_factory.__name__, "")
> # The subprocess either returned successfully or was killed by a
> signal
> # (due to writing out of bounds), depending on the underlying
> allocator.
> if os.name == "posix":
> assert res.returncode <= 0
> else:
> res.check_returncode()
> > assert res.stderr == ""
> E assert 'Fatal Python...in <module>\n' == ''
> E + Fatal Python error: Segmentation fault
> E +
> E + Current thread 0x0000000102009e00 (most recent call first):
> E + File "<string>", line 12 in <module>
> /usr/local/lib/python3.9/site-packages/pyarrow/tests/test_memory.py:245:
> AssertionError
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
