about summary refs log tree commit homepage
path: root/KNOWN_ISSUES
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2010-03-24 12:40:02 -0700
committerEric Wong <normalperson@yhbt.net>2010-03-24 12:40:02 -0700
commit105d9f8b87b0667686ba13960f734b90f3055977 (patch)
tree73f749e9b8a219c9aa8bfec40f98b2761c2b361c /KNOWN_ISSUES
parent36d0fa866ac696ee8acde74f2cffccd06ab8e816 (diff)
downloadunicorn-105d9f8b87b0667686ba13960f734b90f3055977.tar.gz
We're one of the few forking apps that run into this rarely used
feature, so we'll document it here.
Diffstat (limited to 'KNOWN_ISSUES')
-rw-r--r--KNOWN_ISSUES8
1 files changed, 8 insertions, 0 deletions
diff --git a/KNOWN_ISSUES b/KNOWN_ISSUES
index e83e34e..83a450d 100644
--- a/KNOWN_ISSUES
+++ b/KNOWN_ISSUES
@@ -3,6 +3,14 @@
 Occasionally odd {issues}[link:ISSUES.html] arise without a transparent or
 acceptable solution.  Those issues are documented here.
 
+* Under Ruby 1.9.1, methods like Array#shuffle and Array#sample will
+  segfault if called after forking.  This is fixed in trunk (r26936) and
+  should be backported to the next 1.9.1 stable release (after p378).
+  Until then, it is advisable to call "Kernel.rand" in your after_fork
+  hook to reinitialize the random number generator.
+
+  See http://redmine.ruby-lang.org/issues/show/2962 for more details
+
 * When using "preload_app true", with apps using background threads
   need to restart them in the after_fork hook because threads are never
   shared with child processes.  Additionally, any synchronization