[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 63548] Juk sucks insane amounts of memory
From:       "Iván" "Sánchez" Ortega <ivansanchez () wanadoo ! es>
Date:       2003-10-31 16:10:44
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=63548     




------- Additional Comments From ivansanchez@wanadoo.es  2003-10-31 17:10 -------
Subject: Re:  Juk sucks insane amounts of memory

A fecha Friday 31 October 2003 16:50, Scott Wheeler escribió algo así como:

> Are you sure that you're checked for *non* shared memory? 

Sure, while Juk was loading songs, I had ksysguard handy. The virtual memory 
map of juk grew up to 220 MB or so, and the resident emory grew up to 200 MB. 
Afterwards, I killed juk's window.

> i.e. if you have 
> Qt and KDE, id3lib, etc compiled with full debugging symbols the amount of
> shared memory being used would be especially high...

Nope. I get the KDE-CVS snapshot from oberlin.cems.umn.edu , and they compile 
without debugging symbols, AFAIK.

> Also, are you checking just after an import or on an instance where the
> items were restored from the cache?  I noticed (and fixed) an issue
> recently where imported items (i.e. the first time that they're read) were
> taking significantly more memory than restored items.

I'm starting Juk with a blank playlist, and then adding a directory with 
several thousand songs. Perhaps that fits into the "they are read for the 
first time", if I've understood you.

Let's wait for another more recent CVS snapshot to appear in the mirror...
[prev in list] [next in list] [prev in thread] [next in thread]