https://bugzilla.novell.com/show_bug.cgi?id=746767
https://bugzilla.novell.com/show_bug.cgi?id=746767#c0
Summary: konsole-4.7.2-2.3.1.i586 causing Xorg to eat CPU. Top
shows 90+ %
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86
OS/Version: openSUSE 12.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE4 Applications
AssignedTo: kde-maintainers@suse.de
ReportedBy: markh@compro.net
QAContact: qa@suse.de
Found By: ---
Blocker: ---
Created an attachment (id=475904)
--> (http://bugzilla.novell.com/attachment.cgi?id=475904)
sample c program that will produce the bug when executed
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0.1) Gecko/20100101
Firefox/9.0.1
konsole-4.7.2-2.3.1.i586 is causing Xorg to eat CPU time. Top shows 98% for
Xorg after executing the following c program. Also attached.
#include
#include
#include
//
// compile with #gcc pgm.c
// execute with #./a.out
//
int32_t main()
{
int32_t i;
char acr1[3] = {0x0d, 0x0d, 0x0a};
char acr3[44] =
{ 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x1b,
0x5b, 0x35, 0x6d, 0x00, 0x00, 0x00, 0x00, 0x1b,
0x23, 0x33, 0x00, 0x00, 0x00, 0x00, 0x00, 0x20,
0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x57, 0x65,
0x6c, 0x63, 0x6f, 0x6d, 0x65, 0x20, 0x20, 0x20,
0x20, 0x20, 0x20, 0x20 };
char acr4[44] =
{ 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x1b,
0x23, 0x34, 0x00, 0x00, 0x00, 0x00, 0x00, 0x20,
0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x57, 0x65,
0x6c, 0x63, 0x6f, 0x6d, 0x65, 0x20, 0x20, 0x20,
0x20, 0x20, 0x20, 0x20, 0x1b, 0x5b, 0x32, 0x35,
0x6d, 0x00, 0x00, 0x00 };
printf("\n");
for (i = 0; i < 44; i++)
putc(acr3[i], stdout);
for (i = 0; i < 3; i++)
putc(acr1[i], stdout);
for (i = 0; i < 44; i++)
putc(acr4[i], stdout);
for (i = 0; i < 3; i++)
putc(acr1[i], stdout);
printf("\n\n");
return 0;
}
Using different fonts can eliminate the problem. Using the following fonts will
produce the problem every time.
Misc Console, Console, Fixed Misc.
The following fonts will NOT cause the bug.
Adobe Courier, terminal bitstream.
Also, if focus is taken away from the konsole session, the CPU time drops back
to normal. The konsole session can also be brought back to normal operation
using the "reset" command. Until you do a reset command, CPU time for Xorg is
so high you can barely type in the konsole window.
Neither xterm or Gnome terminal exhibit this anomally.
Reproducible: Always
Steps to Reproduce:
1. Install and launch xosview. It is easier than using top to see CPU time.
2. Open a konsole session and build the c pgm attached. "gcc pgm.c"
3. Set the konsole font to "Misc Console"
4. Execute the pgm built in step 1. "./a.out"
5. Note the CPU time increase. top will indicate that Xorg is the CPU hog.
6. Move focus away from the konsole session and notice CPU time normalize.
7. In the konsole session issue "reset" and also notice CPU time normalize
Actual Results:
After executing step 4 above Xorg becomes a CPU hog and the konsole is "almost"
unusable. If you hold a char down you would think it should repeat at a very
high speed but it won't until Xorg is no longer hogging a CPU.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
