diff options
| author | Caleb Ristvedt <caleb.ristvedt@cune.org> | 2020-05-21 20:30:58 -0500 |
|---|---|---|
| committer | Caleb Ristvedt <caleb.ristvedt@cune.org> | 2020-05-22 14:32:07 -0500 |
| commit | 9af90aafdfd8afd5fb7b5377ca5daf2215d38d7a (patch) | |
| tree | 11e4ec1c025c6e8e1d0dcd94072983d8f06131a5 /gnu/packages/patches/guile-fibers-destroy-peer-schedulers.patch | |
| parent | 50ea3135e0948a042cd3b899e970f6ade291a0c2 (diff) | |
| download | guix-9af90aafdfd8afd5fb7b5377ca5daf2215d38d7a.tar guix-9af90aafdfd8afd5fb7b5377ca5daf2215d38d7a.tar.gz | |
gnu: guile-fibers: Add patch to fix resource leak.
guile-fibers@1.0.0 has a resource leak where run-fibers will only destroy one
scheduler, but it creates as many as there are cpu cores by default (see
https://github.com/wingo/fibers/issues/36). This causes the tests to fail on
systems with many cores, and can cause guile to crash under certain
circumstances. This fixes that resource leak. At present neither git master
nor the latest release has fixed this yet.
* gnu/packages/patches/guile-fibers-destroy-peer-schedulers.patch: New patch.
* gnu/local.mk: Add it to the list of patches.
* gnu/packages/guile-xyz.scm (guile-fibers): Use it.
Diffstat (limited to 'gnu/packages/patches/guile-fibers-destroy-peer-schedulers.patch')
| -rw-r--r-- | gnu/packages/patches/guile-fibers-destroy-peer-schedulers.patch | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/gnu/packages/patches/guile-fibers-destroy-peer-schedulers.patch b/gnu/packages/patches/guile-fibers-destroy-peer-schedulers.patch new file mode 100644 index 0000000000..8bb7153153 --- /dev/null +++ b/gnu/packages/patches/guile-fibers-destroy-peer-schedulers.patch @@ -0,0 +1,24 @@ +Fibers 1.0.0 has a bug in run-fibers in which peer schedulers aren't destroyed - +so if you had 4 cores, 1 would be destroyed when run-fibers returned, but the +other 3 would stay around. Each scheduler uses 3 file descriptors, so for +machines with many cores, this resource leak adds up quickly - quickly enough +that the test suite can even fail because of it. + +See https://github.com/wingo/fibers/issues/36. + +This fixes that. It should be safe to destroy the peer schedulers at the given +point because the threads that could be running them are all either dead or the +current thread. + +As of May 21, 2020, this bug still existed in the 1.0.0 (latest) release and in +git master. +--- a/fibers.scm 2020-05-21 18:38:06.890690154 -0500 ++++ b/fibers.scm 2020-05-21 18:38:56.395686693 -0500 +@@ -137,5 +137,6 @@ + (%run-fibers scheduler hz finished? affinity)) + (lambda () + (stop-auxiliary-threads scheduler))))) ++ (for-each destroy-scheduler (scheduler-remote-peers scheduler)) + (destroy-scheduler scheduler) + (apply values (atomic-box-ref ret)))))) + |