CPU usage goes up in preference page

[Hoj]

I'm using Inkscape 0.91pre2 r13516, on Windows 8.1 x64.

In preference window, when I navigate left panel by arrow (up, down) keys, cpu usage goes up to maximum.
High cpu usage status ended when I moved mouse pointer a little.

[jazzynico (jazzynico)]

Not reproduced on Crunchbang Waldorf (Debian stable based distro), Inkscape trunk revision 13576. CPU usage stays low (~2%).

[jazzynico (jazzynico)]

@Hoj - Do you use a 64 bits or 32 bits version of Inkscape?

[Hoj (solum5013)]

I use 64bit version of Inkscape.
I can reproduce this situation, but not irritated by that.

[jazzynico (jazzynico)]

Not reproduced on Windows XP (32 bits), Inkscape trunk revision 13578.

[Formerly Kevin Yin, now disabled (kyin)]

Reproduced on Inkscape 0.91pre2 r13516, on Windows 8.1 x64 (exact same setup as original reporter). Spamming left and right arrow keys in the left panel causes CPU usage to go to 25%, even though nothing else happens.

[Formerly Kevin Yin, now disabled (kyin)]

A difference: when I stop pressing left and right, CPU usage goes back to 0%. It isn't a permanent 25% usage.

[Formerly Kevin Yin, now disabled (kyin)]

More general reproduction behavior:
Pressing any key in Inkscape, anywhere, will give maximum CPU usage. There are no requirements other than pressing a key and not moving the mouse.

Seen on some revision past 0.91pre2, 64 bit build, on Windows 8.1. Also seen on 0.48.4 x86 on Windows 8.1.
Not reproduced on 0.48.4 on Ubuntu in VMWare.

[Formerly Kevin Yin, now disabled (kyin)]

There are some differences between the various keys. Modifier keys such as Ctrl and Alt only require a KeyDown to max the CPU. Other keys, such as letters, numbers, and spacebar, require both a KeyDown and KeyUp before the CPU activity will max.

[su_v (suv-lp)]

Bug #1385773 “high CPU usage on pressing any key in Windows” summarizes the issue more precisely - linking as duplicate to newer report bug #1385773.

If you disagree and think this was done in error, please add a comment here (bug #1376484) and revert the duplicate status.