[Mono-bugs] [Bug 61522][Maj] New - Mono spawns threads by itself and freezes machine
Wed, 14 Jul 2004 03:35:04 -0400 (EDT)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by email@example.com.
--- shadow/61522 2004-07-14 03:35:04.000000000 -0400
+++ shadow/61522.tmp.28905 2004-07-14 03:35:04.000000000 -0400
@@ -0,0 +1,53 @@
+Product: Mono: Runtime
+OS Details: Slackware 10
+Summary: Mono spawns threads by itself and freezes machine
+Description of Problem:
+After launching *any* Mono application (including MonoDoc or Muine or any
+other one) and then closing the application, mono respawns itself new
+Mono threads, each one taking up to 12 MBs of RAM. When I kill one of
+them, one new is re-generated automatically (it is copying itself,
+because I had even removing the /usr/bin/mono executable, and it was
+After a while, there are more than 20-25 Mono threads/pids there, that
+make the machine to run out of memory and even crash completely my
+Previous versions of Mono did NOT have that behavior, this is a problem
+introduced on Mono 1.0. The only thing I did different this time was to
+simply compile Mono and its assosiated libs with the athlon-xp
+Steps to reproduce the problem:
+1. Run any mono app.
+2. Close that mono app.
+3. Wait 2-3 seconds, and then mono will start respawning new mono threads
+of itself under the process group "sh".
+After a while, it clongs your machine.
+To shut down itself and not respawn new threads.
+How often does this happen?
+Slackware 10, kernel 2.4.26, 512 MB RAM, AthlonXP, mono and its libs/apps
+were compiled with -mcpu and -march as "athlon-xp".