From 7a65d53b23941d2e9436493547be65e13cdcbcbc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gonzalo=20Tornar=C3=ADa?= Date: Sat, 30 Mar 2024 22:12:24 -0300 Subject: [PATCH] Workaround for multiprocessing shared memory limits This affects musl libc and macos, see: https://github.com/sagemath/sage/pull/36741#issuecomment-2027357414 We are working on a better fix to avoid using multiprocessing in sage.features, but this will do meanwhile. There is agreement that disabling the lock is completely harmless, since the counter is not really used for anything; disabling the lock fixes the issues that we had on 10.4.beta0. --- src/sage/features/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/sage/features/__init__.py b/src/sage/features/__init__.py index 6af9413e55a..a8b11ef7db5 100644 --- a/src/sage/features/__init__.py +++ b/src/sage/features/__init__.py @@ -162,7 +162,7 @@ def __init__(self, name, spkg=None, url=None, description=None, type='optional') # shared among subprocesses. Thus we use the Value class from the # multiprocessing module (cf. self._seen of class AvailableSoftware) from multiprocessing import Value - self._num_hidings = Value('i', 0) + self._num_hidings = Value('i', 0, lock=False) try: from sage.misc.package import spkg_type