Moving gradient handles causes inkscape to crash

Bug #333405 reported by fireclown
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Undecided
Diederik van Lierop

Bug Description

Using Inkscape on Win32 with latest dev build.

When applying a radial or vertial or horizontal gradient in inkscape to a shape and then selecting on of the gradiant handles and moving or rotating the gradient causes inkscape to crash and close.

Below is the message from the debug program when ran through (gdb)

Program received signal SIGSEGV, Segmentation fault.
0x7c90e8c5 in strchr () from C:\WINDOWS\system32\ntdll.dll
(gdb) bt
#0 0x7c90e8c5 in strchr () from C:\WINDOWS\system32\ntdll.dll
#1 0x00000000 in ?? ()
(gdb)

Woo hoo found a bug :) your page is right it is fun. Thnx for the great work on an amazing program!

Revision history for this message
Yann Papouin (yann-papouin) wrote :

See for more information : http://www.nabble.com/Gradient-manipulation-is-crashing-in-current-revision-to22076147.html

bulia byak wrote:
The offending commit was 20698, and I forwarded this to Diederik who did this commit (so, this is in fact related to snapping after all...)

Changed in inkscape:
assignee: nobody → mail-diedenrezi
status: New → Confirmed
Revision history for this message
Diederik van Lierop (mail-diedenrezi) wrote :

Are you using Inkscape20745-0902212125.7z or Inkscape20757-0902212125.7z? Or did compile yourself? Looking at the time of reporting you might be using the rev. 20745. This bug might have been fixed in 20750 though. If not then it's a apparently another bug, in which case I will look into it!

Revision history for this message
fireclown (glyn-chariot) wrote :

Im using the latest Win32 .7zp Dev build : http://inkscape.modevia.com/win32/Inkscape20757-0902231544.7z, Which i have extracted to the latest Inkscape Win32 Dev Build: http://inkscape.modevia.com/win32/Inkscape20711-0902171746.7z

I think this is what im supposed to do as it looks like you have updated parts of the main build rather than host the whole build again.

Still crashes when the gradiant is moved witht he gradiant handles, but if you unselect move gradian with shape and move the shape to get the gradiant angle you like, there is no crash, and if you select the gradian node and move it with the cursor key again no crash :)

Thanks for all the work you guys do I think its absolutely brilliant!!

Revision history for this message
Diederik van Lierop (mail-diedenrezi) wrote :

No, we only do complete and clean nightly builds as far as I know. Now I looked at it more carefully I noticed that the files are only 6 MB in size and that they do not contain any executables, so apparently the build process is not working properly. This also means that you're probably still testing an older version.

I've notified the maintainer about this issue, so this will probably be fixed within a day or so. It would be very much appreciated if you could try again after that.

Thanks for your effort!

Revision history for this message
Yann Papouin (yann-papouin) wrote :

It is not crashing anymore for me in rev#20595, the new snap tool tip is displayed (I don't know why, but sometimes it is not displaying the final "L" letter in "Handle to gradient leve").

About this, apparently the help text uses the guide color (blue) to be displayed, is there a way to display it with a negative mode (currently I'm not able to see a blue text over a black or red shape) if not, maybe adding a white stroke to it will help ?

bbyak (buliabyak)
Changed in inkscape:
status: Confirmed → Fix Released
Revision history for this message
Diederik van Lierop (mail-diedenrezi) wrote :

@Yann: I noticed something similar, with the bottom of the text-box getting truncated. I expect that the relatively new SPCanvasText class is doing something wrong when calculating the text-box size. I'm not going to track this one down, there are far more important bugs to tackle ;-). This will get solved someday...

W.r.t. the tooltip text not being readable on a blue background: could you please file a separate bug for this? This way it will more likely to be noticed, and then we can close this bug after fireclown has confirmed the original bug has been solved.

Revision history for this message
Yann Papouin (yann-papouin) wrote :
Revision history for this message
fireclown (glyn-chariot) wrote :

Sorry fellas, im not ignoring this bug just waiting for the new full win32 dev build to go live I know it takes a few days :) so just giving you feedback so you know where everythings up to. Pretty sure it will have been fixed seen I was running and old version, I will let you know as soon as I know so you can close this bug. This bug reporting is better than licensed software :) well done guys

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.