[Mono-devel-list] Garbage Collection problem

Jörg Rosenkranz joergr at voelcker.com
Tue Sep 30 09:58:40 EDT 2003

Hi all,

We are developing a server application which creates and destroys 
many objects during it's lifetime. Sometimes there is a heavy increase
of memory consumption because many large objects are handled 
simultanously. Running this application we recognized that the heap 
size doesn't decrease after such a heavy load. There is nothing in 
memory but memory usage is about 250 MB!

The attached sample demonstrates this behaviour:
It creates many strings and causes a memory usage of about 30 MB.
Running the sample in MS.NET after removing the references and 
triggering garbage collection the heap is very small again. Running 
under Mono/Linux the heap stays at 30 MB. The same applies to 
physical memory usage of the process.

I think this behaviour depends on the different garbage collector 
implementations (compacting/non compacting). What can be done to 
work around this problem? Or is it a Mono bug?

Thanks in advance,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GCTest.cs
Type: application/octet-stream
Size: 917 bytes
Desc: GCTest.cs
Url : http://lists.ximian.com/pipermail/mono-devel-list/attachments/20030930/591b0061/attachment.obj 

More information about the Mono-devel-list mailing list