Bug 116526

Summary: bad memory leak in korgac
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Bart Whiteley <bwhiteley>
Component: KDEAssignee: E-mail List <kde-maintainers>
Status: RESOLVED INVALID QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None    
Version: Beta 4   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: strace of korgac

Description Bart Whiteley 2005-09-12 15:05:06 UTC
I just noted that korgac was using 343MB RAM on my box.  I'm not sure how 
it got into this state, since I don't really even use it.
Comment 1 Dirk Mueller 2005-09-13 15:32:32 UTC
reproduceable? strace? gdb bt ? any instructions on how to reproduce or where 
the machine is? 
 
 
Comment 2 Will Stephenson 2005-09-13 15:56:07 UTC
Bart, do you have an very large GroupWise calendar loaded in Kontact?  Might 
be that korgac is just doing its job (handling calendar reminders and alarms 
when Kontact is not running). 
Comment 3 Bart Whiteley 2005-09-13 16:20:20 UTC
I'll see if I can get more information if I catch it again.  I don't  
have a very large calendar.  Actually, when it was misbehaving I had 
changed my corp. password, so the login was failing.  Maybe that's  
related to the problem.  So, there was no calendar loaded from the server,  
but there were potentially a bunch of failed login attempts.  
 
I just fixed the password on the client, and now korgac sits about 30MB 
once it has pulled the calendar and settled down.  
Comment 4 Bart Whiteley 2005-09-22 18:01:30 UTC
I caught it misbehaving again.   
stack trace:  
#0  0xffffe410 in __kernel_vsyscall () 
#1  0x40eb1f2d in ___newselect_nocancel () from /lib/tls/libc.so.6 
#2  0x407f6c33 in QEventLoop::processEvents () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#3  0x4085f903 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 
#4  0x4085f7e6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 
#5  0x4084833f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 
#6  0x08051e66 in ?? () 
#7  0xbfb6b2a4 in ?? () 
#8  0x00000001 in ?? () 
#9  0x00000001 in ?? () 
#10 0x00000000 in ?? () 
#11 0x00000000 in ?? () 
#12 0x00000001 in ?? () 
#13 0x08057ccd in vtable for QGList () 
#14 0x00000000 in ?? () 
#15 0x08057cba in vtable for QGList () 
#16 0x08057ca6 in vtable for QGList () 
#17 0x08057b0f in vtable for QGList () 
#18 0xbfb6b2a8 in ?? () 
#19 0x40e60ea6 in malloc () from /lib/tls/libc.so.6 
#20 0x40e0fea0 in __libc_start_main () from /lib/tls/libc.so.6 
#21 0x08050ac1 in ?? () 
 
 
 
Comment 5 Bart Whiteley 2005-09-22 18:07:01 UTC
Created attachment 50675 [details]
strace of korgac

top currently shows: 
  PID USER	PR  NI	VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
10040 bart	16   0	513m 169m  10m S  0.0 16.8   5:42.44 korgac
Comment 6 Stephan Kulow 2006-02-09 21:03:14 UTC
ok, closing. I know it's not fair, but we have too many inreproducible bugs and we need to concentrate on those we _can_ fix at the moment.