Movement and other responses erratic

Starting about Dec 19 13:00 -08:00 (PST) my sl client and AV responded to all keyboard motion commands so erratically that it was practically impossible to use. The camera and mouse view commands were also difficult to impossible to use. The setup was:

Viewer: SecondLife_i686_1_18_6_75762_WINDLIGHT
Graphics Card: Nvidia GeForce FX 5700
Graphics Driver: Nvidia-kernel-100.14.19
Distribution: Debian sid

On Dec 20 in the morning after the viewer had not been running overnight I noticed the following in the process table.

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
XXXX 6057 1.9 6.0 618720 94792 ? SLl Dec19 12:59
bin/do-not-directly-run-secondlife-bin -settings settings_windlight.xml -channel Second Life WindLight

I started the viewer and saw the same crippled behavior. I quit the viewer, killed the above process, and started the viewer again. The responses to motion commands and other keyboard input was what I now take to be normal is some sense.

Between Nov 25, when I was born, and Dec 19, I saw the same crippling behavior, perhaps in varying intensity, so consistent/y that I suspect that extraneous processes may have been frequently interfering with the operation of the viewer. It would appear that the viewer does not always shutdown cleanly and that processes that remain running from an earlier session can interfere with a new viewer session.

Why not make the secondlife startup script kill any remaining secondlife processes before starting a new viewer?

I have experience similar behavior over the past month, since being on sl.

In my case the 1.18.5.x and above viewers, will start using 100% cpu, in the user and system level as reported by KDE system guard. Usually I see no extra process left behind.

This behavior occurs regularly if I do any of the following while running the client,

1)Minimize then maximize the viewer, this will typically happen on the first minimize / maximize sequence, sometimes it will not occur on the first minimize / maximize sequence. But will happen

2)I run dual monitors, if I move the viewer from one monitor to another, cpu 100% every time

3)Certain programs mainly graphics like Blender will cause the viewer, to max out at 100% cpu. IF I start blender with the viewer running as well. Not sure if this is normal on not, or perhaps blender is doing something strange as well.

Graphics card: GeForce Go 7300, Driver 169.07 (note the above also occurs with the 100.14.19 driver)

Distro: Suse 10.3