Skip to content

Commit 7a65d53

Browse files
committed
Workaround for multiprocessing shared memory limits
This affects musl libc and macos, see: #36741 (comment) 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.
1 parent b693ea9 commit 7a65d53

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/sage/features/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,7 @@ def __init__(self, name, spkg=None, url=None, description=None, type='optional')
162162
# shared among subprocesses. Thus we use the Value class from the
163163
# multiprocessing module (cf. self._seen of class AvailableSoftware)
164164
from multiprocessing import Value
165-
self._num_hidings = Value('i', 0)
165+
self._num_hidings = Value('i', 0, lock=False)
166166

167167
try:
168168
from sage.misc.package import spkg_type

0 commit comments

Comments
 (0)