Bug 287978 - Java application cause KDE desktop to be unresponsive.
Summary: Java application cause KDE desktop to be unresponsive.
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-01 10:51 UTC by Dirk Heinrichs
Modified: 2012-01-22 15:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Heinrichs 2011-12-01 10:51:09 UTC
Version:           unspecified (using KDE 4.7.3) 
OS:                Linux

Whenever I run a Java application (Eclipse, Oracle SQL Developer) under KDE, the system becomes unresponsive for some time (up to several minutes) while system load increases considerably until eventually the Kernel's OOM killer kills the Java process.

This never happens under XFCE4.

Reproducible: Always

Steps to Reproduce:
In a KDE session, run eclipse or SQL Developer.

Actual Results:  
System is unusable for some time, until Java application gets killed by OOM killer.

Expected Results:  
Well, a running Java application in a usable desktop.

OS: Linux (x86_64) release 3.0.0-14-generic
Compiler: gcc
Comment 1 Lamarque V. Souza 2011-12-01 11:32:03 UTC
Eclipse is very resource intensive, if your computer does not have enough RAM memory it is going to trash like you described. How much memory does it have?

If there is no memory leak in a KDE program I do not see what we can do about this problem.
Comment 2 Blagovest Zlatev 2011-12-01 13:54:17 UTC
I couldn't reproduce this bug or find duplicates.
Comment 3 Dirk Heinrichs 2011-12-01 14:06:01 UTC
(In reply to comment #1)
> Eclipse is very resource intensive, if your computer does not have enough RAM
> memory it is going to trash like you described. How much memory does it have?

It has 3GiB! Hmm, maybe it's releated to the OpenAFS Client running with an in-memory cache...

I'll check that.
Comment 4 Lamarque V. Souza 2012-01-21 23:31:26 UTC
So, any news about this problem? Should we blame OpenAFS for it?
Comment 5 Dirk Heinrichs 2012-01-22 08:24:21 UTC
(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.
Comment 6 Lamarque V. Souza 2012-01-22 15:15:35 UTC
(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.