From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <frysk-bugzilla-return-1610-listarch-frysk-bugzilla=sourceware.org@sourceware.org>
Received: (qmail 22810 invoked by alias); 21 Mar 2007 20:37:24 -0000
Received: (qmail 22777 invoked by uid 48); 21 Mar 2007 20:37:11 -0000
Date: Wed, 21 Mar 2007 20:37:00 -0000
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Message-ID: <20070321203711.4244.cagney@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug general/4244] New: funit --gc -- run the garbage collector after each test
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact frysk-bugzilla-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:frysk-bugzilla-subscribe@sourceware.org>
List-Post: <mailto:frysk-bugzilla@sourceware.org>
List-Help: <mailto:frysk-bugzilla-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: frysk-bugzilla-owner@sourceware.org
X-SW-Source: 2007-q1/txt/msg00758.txt.bz2
List-Id: <frysk-bugzilla.sourceware.org>

Often there are memory corruption bugs triggered by garbage collection.

Being able to force a garbage collection after each bug would help more quickly
narrow that down.

NB: Triggering a GC is non-trivial, the sequence:
  System.gc(); // please garbage collect when you have a mo'
  Thread.wait (100); // here's a mo'.
works relatively well.

-- 
           Summary: funit --gc -- run the garbage collector after each test
           Product: frysk
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
        AssignedTo: frysk-bugzilla at sourceware dot org
        ReportedBy: cagney at redhat dot com
OtherBugsDependingO 2242
             nThis:


http://sourceware.org/bugzilla/show_bug.cgi?id=4244

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.