Runtime Error and Crash When Moving Nodes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Inkscape |
New
|
Undecided
|
Unassigned | ||
Bug Description
I'm having a consistent bug occurring with what seems like a fairly simple drawing. It's causing the program to crash with the message "Microsoft Visual C++ Runtime Library, Runtime Error".
I created a line using the freehand line tool, duplicated it, moved it, combined the two, and then when I was trying to move some of the nodes around it crashes. The freehand lines do not form a closed shape, but only have a few dozen nodes - so they are not complex.
I can re-create this crash almost 100% of the time by loading the drawing, selecting a few of the nodes next to the inner left side of the mouth, and trying to move them.
I am using Windows 10, and Inkscape 0.92
I am enclosing a link to a screenshot of the crash, and the file that I was working with that I can use to re-create the crash.
I have a work-around, so its not urgent for me.
https:/
| Brynn (brynn4inks-deactivatedaccount) wrote | #1 |
| Brynn (brynn4inks-deactivatedaccount) wrote | #2 |
| Alvin Penner (apenner) wrote | #3 |
I've reproduced it. I haven't had a crash which produces the same error message, but I've achieved a fatal freeze.
Initially I thought the problem was related to being at a high zoom. But I've been able to reproduce it as low as 1600% zoom (and as high as the maximum zoom (25600%)).
Placing the Node tool mouse pointer in approx the blue circle in the attached zc1.png, the pointer changes to the "finger" (erroneously in my view). When I click-drag to select all 3 nodes, I see the same ghosting which is reported by the OP (see zc3.png). And the path shoots off the page.
I don't know why the finger is showing up when the mouse is clearly not over the path. But what seems to be happening, is that Inkscape thinks the mouse is over the path. And when I drag to make the selection, it's actually editing the path.
I also don't know why such a small movement of the mouse results in such a huge change of the path. See what it looks like at 100% zoom, in zc2.png. A movement of the mouse less than a pixel (while zoomed) creates (in my tests) a "curve" in the path as long as 500 pixels. (500 out and 500 back)
At first I was thinking that the path must be shooting so far for the OP, that it was making the file so huge that it crashed. But since I've achieved a fatal freeze (with 16 gb RAM), I think something else must be happening to cause the freeze or crash, something besides, the erroneous "finger" and exaggerated path edit. (Maybe what I've heard referred to as a "memory leak"?) But of course I'll have to leave that to the experts to determine the cause.
Maybe there is more than 1 problem happening here? I'm not sure. For the record,
Window 7 Pro, 64-bit, 16 gb RAM, Inkscape 0.92.1, 64-bit, exe installer
Any additional info needed, just ask :-)
Thank you very much!