Whiptail ubuntu 10.04 lts up to 99% CPU

Step #1: First, you need to find out process PID (process id)

Use ps command or pidof command to find out process ID (PID). Syntax:
ps aux | grep processname
pidof processname

For example if process name is lighttpd, you can use any one of the following command to obtain process ID:
# ps aux | grep lighttpdOutput:

lighttpd  3486  0.0  0.1   4248  1432 ?        S    Jul31   0:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
lighttpd  3492  0.0  0.5  13752  3936 ?        Ss   Jul31   0:00 /usr/bin/php5-cg

OR use pidof command which is use to find the process ID of a running program:
# pidof lighttpdOutput:

3486

Step #2: kill process using PID (process id)

Above command tell you PID (3486) of lighttpd process. Now kill process using this PID:
# kill 3486
OR
# kill -9 3486
Where,

    * -9 is special Kill signal, which will kill the process.

 PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
27953 root      20   0  3296 1216  836 R   92  0.0  42161:17 whiptail
31656 root      20   0  3296 1268  896 R   90  0.0  10080:55 whiptail

ps aux | grep whiptail
root     18805  0.0  0.0   1856   572 pts/2    R+   12:29   0:00 grep whiptail
root     27953 91.6  0.0   3296  1216 ?        R    Aug23 42255:23 whiptail --ba
cktitle Package configuration --title Configuring otrs2 --output-fd 11 --passwor
dbox -- Please provide the password for the administrative account with which ?t
his package should create its MySQL database and user.??Password of the database
's administrative user: 11 75
root     31656 44.6  0.0   3296  1268 ?        R    Sep08 10174:56 whiptail --ba
cktitle Package configuration --title Configuring otrs2 --output-fd 11 --passwor
dbox -- Please provide the password for the administrative account with which ?t
his package should create its MySQL database and user.??Password of the database
's administrative user: 11 75

HI,


I was a app bad closed!!!

After kill the app..everything was ok

Unfortunately after killing the process everything IS NOT OK. You have merely sorted out the symptoms (excessive processor use), but this issue will return either periodically, or after your next restart. You need to sort out the cause of the problem as detailed above. Either remove or correctly configure your Open Source Ticket Request system.

If by 'killing the app' you actually mean that you have removed the Open Source Ticket Request System, then you should be OK, and I apologise for the misunderstanding of your post.

I found the correct program