Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Before starting motion, everything is ok.
While motion is running, everything is ok.
After motion is stopped, CPU-load goes up and stays high.
Restarting motion brings CPU-load again down, back to normal level.
It's the process khubd that causes the high CPU-load after stopping motion.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
No effective solution found yet, and khubd isn't killable.

   * What was the outcome of this action?
One has to reboot the machine after stopping motion.
This is of course not a practical solution.

   * What outcome did you expect instead?
CPU-load should not go up when motion is stopped.
It is illogical and annoying behaviour that the CPU-load goes up when the
program
terminates.

*** End of the template - remove these template lines ***

control: tags -1 moreinfo
control: tags -1 unreproducible

Hi,

Do you have some more information about this? How do you know this problem is the fault of motion? Does it happen if you use another webcam program (e.g. cheese) or video converter (e.g. ffmpeg)?

X