Wacom's message queue puts CPU to 100%
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Rev. 20535 and earlier on XP.
When the node tool is active, and a path with many nodes selected, only a few of it's nodes are displayed on the screen.
The CPU goes into ~100% activity without anything more happening before the cursor is moved outside the Inkscape window (or waiting VERY long time).
Using ctrl-A to select all these nodes also goes extremely much faster, when the cursor is outside the Inkscape window.
Even when nothing is selected, the CPU goes on high activity, when the cursor is in the window.
Removing the mouse/pen from the tablet makes the same change on effectivity as moving the cursor outside the window.
There has been some notes in the past on patching gtk+ to limit the Wacoms message rate, and I also got the impression that the problem was solved permanently in gtk+.
But this is apparently not the case.
Whatever, if this bug is considered to be in in gtk+ or Inkscape, it is really a showstopper, if you are not aware of the reason and what to do.
summary: |
- Message que/Wacom blocking process on XP. + Message queue/Wacom blocking process on XP. |
tags: | added: tablet |
summary: |
- Message queue/Wacom blocking process on XP. + Wacom's message queue puts CPU to 100% |
tags: | added: performance |
tags: | added: node-editing |
Changed in inkscape: | |
status: | Incomplete → New |
Not reproduced on Vista, Inkscape 0.47.
Could you please confirm you still have this issue with 0.47? inkscape. modevia. com/win32/ ?M=D (the Windows devlibs, including gtk+, have been updated recently)?
If so, could you test a snapshot at http://
Thanks!