# 4.2. Known bugs and problems

- kpm sometimes dies with a segmentation fault if more than one process is marked and the list is updated. I've no clue why...

- The info bar and the process list itself are optimized for 12pt fonts. It will look good enough with fonts up to 14pt, but look very ugly for bigger fonts.

- kpm can consume a lot of CPU resources if the update period is too small. On my system (AMD K6PR200) it uses approximatly 5 percent CPU time with an update period of one second. This heavily depends on the total number of processes (all processes, not only those displayed) and can be much higher than this.

- The %CPU number isn't accurate at very short update periods due to timer granularity.

- The WCHAN field isn't correct if a process sleeps in a location outside those in `System.map` (for instance, in a kernel module). In these cases, the last entry in `System.map` will be showed (something like `_end`).

- kpm doesn't handle more than one process with the same PID. This can occur when using CLONE_PID with the clone() system call.