Bug 105784

Summary:	mono eating up system resources
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Fabrizio Magni <fabrizio.magni>
Component:	Mono	Assignee:	E-mail List <bnc-team-mono>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Blocker
Priority:	P5 - None	CC:	aj, m.camen
Version:	Beta 2
Target Milestone:	---
Hardware:	i686
OS:	All
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Fabrizio Magni 2005-08-19 09:41:12 UTC

After starting KDE mono (running in debug mode) eats up most of my system resources.

Up to 54% of my CPU (pentium4) and 34% of
my memory (256M).

My system is almost unusable until I kill all the mono processes (I
couldn't find any way to shut it down gracefully).

After posting on the beta mailing list they asked me to fill a bug.

New to this so I'm not sure what I have to provide in order to help you.

Make me know if you need logs or if I have to perform tests.

Regards
Fabrizio

Comment 1 Jos van den Oever 2005-08-20 16:45:46 UTC

confirm: up to 40% on my machine so far (also 256 mb) 
 
system is relatively usable so far, but will kill mono anyway. This is 
unacceptable. Also while running  
 
mono --debug /usr/lib/beagle/BuildIndex.exe 
--target /var/cache/beagle/indexes/documentation --recursive 
--enable-text-cache --allow-pattern 
*.xml,*.html,*.docbook /usr/share/doc /opt/kde3/share/doc /opt/gnome/share/gnome/help

Comment 2 Marcus Camen 2005-08-20 16:48:38 UTC

Can you check if the beagle-index RPM is installed?

Comment 3 Fabrizio Magni 2005-08-21 07:06:25 UTC

# rpm -qa|grep beagle
beagle-0.0.13-6
libbeagle-0.0.13-6

No beagle-index for me.

Comment 4 Andreas Jaeger 2005-08-22 18:23:54 UTC

Similar problem here - using 990 MB out of 1 GB :-(

I do not have beagle-index either.

raising priority, this is not acceptable.

Comment 5 Marcus Camen 2005-08-22 18:31:34 UTC

Ok, I have beagle-index installed and CPU load of beagle goes to 80%. But it 
doesn't take so much memory.

Comment 6 Mark Gordon 2005-08-23 12:33:18 UTC


*** This bug has been marked as a duplicate of 105796 ***

Comment 7 Andreas Jaeger 2005-08-30 08:27:12 UTC

Just a comment to #4: AFter deleting .beagle everything works again.  My problem
was not related to beagle-index.