Niknak wrote > ..... > Why does the memory consumed by the Mono process keep growing? > > Mono currently uses a conservative, non-moving, non-compacting garbage > collector. This means that the heap is not compacted when memory is > released. This means that applications can produce memory allocation > patterns that will effectively make the process grow, just like C, C++, > Perl, Python applications would. > ..... > ASP.NET in Mono is particularly vulnerable to this kind of memory problems > because it is easy for developers to define APIs that transfer large blobs > of data like entire image files, these would allocate a lot of memory that > can easily be fragmented. > ...... > Anyone else experienced this or have any work arounds?
I would suggest just using the SGEN garbage collector instead of the 'old' Boehm one. You can force the Mono fastcgi-mono-server use the SGEN version by using the MONO_OPTIONS environment variable. Make sure the following line is present in whatever script inits your shell: export MONO_ENV_OPTIONS="--gc=sgen" -- View this message in context: http://mono.1490590.n4.nabble.com/Memory-Leak-in-Generic-Handler-tp4657696p4658599.html Sent from the Mono - ASP.NET mailing list archive at Nabble.com. _______________________________________________ Mono-aspnet-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
