| Summary: | Typing in Kepler is slow and causes high Xorg CPU usage compared to Indigo | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jan Zuchhold <Jan> |
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | arunkumar.thondapu, emond.papegaaij, ericwill, rashid.sarwar, sravankumarl |
| Version: | 4.3 | Keywords: | triaged |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
|
Description
Jan Zuchhold
Having the same problem, Please tell us what is the progress on this issue I use Ubuntu 12.04 regularly and have not seen the high CPU usage problem till now. Sravan, can you please do a comparison between 3.7 and 4.4 and see if there is any noticeable difference in typing performance? Thanks! I tried to reproduce this on ubuntu 13.10 and with normal laptop screen. I am unable to reproduce this problem. Can you please test this on normal Laptop screen (HD screen 720p) and with a display driver other than NVIDIA? Thanks Unfortunately I only have NVIDIA-GPUs to test with, as Intel and AMD drivers always created a lot of problems on Linux for me. I was unable to reproduce this problem within VMware Workstation using the vmware-xorg-driver: It works just fine, even though the host is showing the problem. Testing with such low resolutions as 720p seems unrealistic, even more now that 4K displays (3840x2160, 8 megapixels!) are affordable. I guess this is some inefficiency in drawing operations that shows a lot more on higher resolutions. Hi, This problem looks very much similar to https://bugs.eclipse.org/bugs/show_bug.cgi?id=397291 Can you please check with the solution provided in comment#19 https://bugs.eclipse.org/bugs/show_bug.cgi?id=397291#c19 Thanks Sravan That AccelMethod option is driver dependent and the NVIDIA driver does not support it: (WW) NVIDIA(0): Option "AccelMethod" is not used (from /var/log/Xorg.0.log) There were a lot different issues with 100% CPU usage in the past: some were Webkit1 related, some were related to Oxygen-GTK. These things are both gone now, so I think it's time to close this bug. Please file a new bug against 4.8 if the issue occurs on GTK3.22. |