http://qa.mandrakesoft.com/show_bug.cgi?id=3448
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2003-03-27 22:35 -------
with 9.1 final
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
I saw that X had a 0 nice value.
It previously had -10 nice value (9.0 release).
Having a 0 nice value gived me some problems
when I created a software with a high framerate (24 frames/s).
My X server could not follow this rate for the given window size
and it become overloaded
because it used the most part of its time
in managing memory.
The more it became late,
the more it had to manage memory (not displayed frames)
and the more it became slow.
It bringed my computer to crash.
I agree that my software should adapt its framerate
(what I did later),
but the problem is that
an non root user crashed the system
(i.e. a developper testing a new software) !
Think at the other users
which used the node I crashed !
Simply changing the nice value to -1
fixed the problem.
Previous (r 9.0) -10 nice value was good.
I think that all what handles
user interface have to be
more near from real time.
In case X server is not used,
it will not consume CPU time.
For application server use,
simply shutdown X
or manually increase X nice value.
