From 9c1b774a3acbd217a375dfa2e6d608235246aeb0 Mon Sep 17 00:00:00 2001 From: simonmar Date: Tue, 28 Jun 2005 13:44:28 +0000 Subject: [PATCH] [project @ 2005-06-28 13:44:28 by simonmar] Add a comment that grabbing all the capabilities before GC causes the thread->capability hash table to acquire multiple entries for the current thread, which seems to be harmless. --- ghc/rts/Schedule.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/ghc/rts/Schedule.c b/ghc/rts/Schedule.c index 8a21d7b..df1cace 100644 --- a/ghc/rts/Schedule.c +++ b/ghc/rts/Schedule.c @@ -1906,6 +1906,11 @@ scheduleDoGC( rtsBool force_major ) // actually did the GC. But it's quite hard to arrange for all // the other tasks to sleep and stay asleep. // + // This does mean that there will be multiple entries in the + // thread->capability hash table for the current thread, but + // they will be removed as normal when the capabilities are + // released again. + // // Someone else is already trying to GC if (waiting_for_gc) return; -- 1.7.10.4