[Bug 287978] Java application cause KDE desktop to be unresponsive.

Lamarque V. Souza lamarque at kde.org
Sun Jan 22 15:15:35 GMT 2012


https://bugs.kde.org/show_bug.cgi?id=287978


Lamarque V. Souza <lamarque at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |INVALID




--- Comment #6 from Lamarque V. Souza <lamarque kde org>  2012-01-22 15:15:35 ---
(In reply to comment #5)
> (In reply to comment #4)
> > So, any news about this problem? Should we blame OpenAFS for it?
> 
> Oh, sorry, forgot to write a followup. After switching OpenAFS from memcache to
> a disk-based cache, the problems went away.
> 
> However, I still think that even the remaining 2GiB in the memcache case should
> be more than enough RAM for a desktop system.

That is what everybody wanted. My Linux in runlevel 1 takes about 290 MB.
Runlevel 1 means no Xorg, no KDE desktop, nothing running, but the kernel and
the command shell. With the login window (kdm) running it takes about 740 MB.
After logging in and launching eclipse it takes a little more than 1 GB.
Launching kmail it takes about 1.01 GB (kmail seems not to take that much ram
memory). After launching chromium with four tabs the memory usage sky rocket to
almost 1.9 GB of RAM. Dependending on the program set you use 2 GB is not
enough.

I must say that I am a little disappointed with the ram usage in this new
notebook with Intel Core i7. I also own an old notebook with a Turin64
processor and in that old notebook the ram usage is much better than this one
with the same set of programs running. The difference is about 300 MB of ram,
which is more than one third of program set's ram memory when running on the
notebook with Core i7. I use Gentoo optimized for each processor, maybe the
optmizations for Intel processor causes this effect, I do not know.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list