Inkscape version 0.48.2 r9819
Operating system: Arch Linux
cat /proc/version: Linux version 3.0-ARCH (tobias@T-POWA-LX) (gcc version 4.6.1 20110819 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Aug 30 07:32:23 UTC 2011
Desktop environment / window manager: KDE 4.7.1-1 (kdeplasma, etc..)
The problem: When selecting certain combinations of nodes on a complex path and clicking the "Join endnodes with new segment" button, Inkscape's CPU usage rises to 99%, the application becomes unresponsive and stops updating its window, autosave stops working, no emergency save is generated, and the program needs to be manually SIGTERM/SIGKILLed to get rid of it.
Expected behavior: Probably doing nothing; the nodes selected can't really be joined in a sensible way. Generally Inkscape simply ignores the button click and gives no significant feedback if the nodes can't be joined.
I assume that the bug has gone unreported because it's triggered by a nonsense request; there isn't really any good reason to select these combinations of nodes and try to join them in this way. I first encountered the bug when I was trying to join some nodes in a particularly crowded section of a complex path, and had accidentally selected nodes from a section of the path much further down the chain but running across the section I was working on.
I am attaching an .svg file that reliably reproduces the problem on my system. Open the file, select the path editor tool, select the only path in the file, select the three nodes clustered very close together near the middle of the path, and click the "Join endnodes with new segment" button (fifth button from the left on my configuration). When I perform these steps, the program becomes unresponsive for longer than forty minutes; I have not waited longer than that before manually killing it.
I'm not really sure what sorts of paths or combinations of nodes generate the bug; I have been able to reproduce it twice (after the first occurence) in otherwise empty documents by drawing a path with many nodes overlapping itself, then randomly moving and adding nodes, selecting random combinations and trying to join them. All instances of the bug have happened with at least three nodes selected, the nodes have been in very close proximity to eachother (relative to the overall size of the path) and the nodes have been from different sections of the same path (IE not adjacent nodes). All three crashes have involved closed paths, as well.
That's all the information that seems relevant right now. If you need more information, just send me an email.
> Expected behavior: Probably doing nothing; the nodes selected can't really be
> joined in a sensible way. Generally Inkscape simply ignores the button click
> and gives no significant feedback if the nodes can't be joined.
Possibly related to this new feature in the node tool of 0.48.x:
«Improved segment join
It is now possible to create a segment between endnodes from different paths. More than one segment can be created at once—the distances between nodes will be used to determine which nodes to join with a segment, with the closest pairs being joined first. When nothing can be joined (less than 2 endnodes in selection), each selected stretch of nodes will have its middle nodes removed, leaving only one segment. »
<http://