This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GC Problems...
- From: Bryce McKinlay <mckinlay at redhat dot com>
- To: Simon Levitt <simon dot levitt at worldpay dot com>
- Cc: java at gcc dot gnu dot org
- Date: Tue, 07 Sep 2004 14:12:50 -0400
- Subject: Re: GC Problems...
- References: <200409061758.28744.simon.levitt@worldpay.com>
Simon Levitt wrote:
I've tried without much success to find any similar problems to this in the
list archives.
Recently I've been invovled in a project to use GCJ as a backend for an
implementation for a COM object.
The primary development environment is under MinGW/MSYS (Using the latest
stable versions + newest binutils) on Win2000.
We've been having a number of problems with the garbage collection, most of
which have been resolved by compiling a recent version (version: 3.5.0
20040824 experimental) of GCC with USE_GLOBAL_ALLOC defined. (The used
gc_config.h file is attached). I'm only compiling the static libraries.
The problem exists in both the COM environment we're running under, and the
simple test case application I'm attaching here, there appears to be a memory
leak.
There is a known leak with thread creation on win32. I'm not sure if it
applies to JvAttachCurrentThread(), but its possible. See
http://gcc.gnu.org/PR14751
I heard Mohan was testing a fix for this, but I'm not sure what the
status is now. I suggest attaching the thread just once instead of
continuously attaching and detaching it.
Regards
Bryce