Inkscape crashed when cutting a polygon from another layer (core dump attached)

Bug #727815 reported by Tom Dignan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
High
Unassigned

Bug Description

I was using inkscape to draw a pencil from rectangles that I turned into paths. The steps were long and elaborate, so I don't recall them all. This happened more than once. I am on a 64 bit machine. I turned on core dumps so I could at least provide some useful information. I hope it is enough to diagnose the problem.

Thanks!

Tags: crash
Revision history for this message
Tom Dignan (tom-dignan) wrote :
Revision history for this message
su_v (suv-lp) wrote :

Please add information about your OS/platform and Inkscape version.

> I hope it is enough to diagnose the problem.

Could you provide a backtrace with gdb instead? If not, a 'steps to reproduce' would be helpful for bug triage.

tags: added: crash
Changed in inkscape:
status: New → Incomplete
Revision history for this message
Tom Dignan (tom-dignan) wrote : Re: [Bug 727815] Re: Inkscape crashed when cutting a polygon from another layer (core dump attached)
Download full text (6.7 KiB)

I got this stack trace by doing gdb `which inkscape` corefile. It
doesn't look helpful to me, but maybe I just don't see it. The problem
occured when using about 7 different layers and trying to cut a
polygon out of one of them. I cannot replicate it, I tried. But it did
happen more than one time while I was working.

(gdb) bt
#0 0x000000000045bc16 in ?? ()
#1 0x00000000006213a4 in ?? ()
#2 0x00007f8f314479b9 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#3 0x00007f8f3145d4d7 in ?? () from /usr/lib/libgobject-2.0.so.0
#4 0x00007f8f3145e7db in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#5 0x00007f8f33125a95 in gtk_signal_emit () from /usr/lib/libgtk-x11-2.0.so.0
#6 0x000000000099090a in ?? ()
#7 0x0000000000990bab in ?? ()
#8 0x0000000000621670 in ?? ()
#9 0x00007f8f31447a6e in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#10 0x00007f8f3145d120 in ?? () from /usr/lib/libgobject-2.0.so.0
#11 0x00007f8f3145e7db in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#12 0x00007f8f33125a95 in gtk_signal_emit () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x0000000000590459 in ?? ()
#14 0x000000000059096d in ?? ()
#15 0x00007f8f32faa9d8 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#16 0x00007f8f31447a6e in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#17 0x00007f8f3145d120 in ?? () from /usr/lib/libgobject-2.0.so.0
#18 0x00007f8f3145e7db in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#19 0x00007f8f3145ef53 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#20 0x00007f8f330c36df in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#21 0x00007f8f330c38bc in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#22 0x00007f8f330c3bf0 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#23 0x00007f8f32fa392d in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#24 0x00007f8f3302ed68 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#25 0x00007f8f32fa3942 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#26 0x00007f8f32fd19af in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#27 0x00007f8f32fa3942 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#28 0x00007f8f3302ed68 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#29 0x00007f8f32fa3942 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#30 0x00007f8f32ef50bb in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#31 0x00007f8f32fa3942 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#32 0x00007f8f32ef50eb in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#33 0x00007f8f32fa3942 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#34 0x00007f8f32fa3942 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#35 0x00007f8f32fa3942 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#36 0x00007f8f32fa3a2b in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#37 0x00007f8f330db53f in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#38 0x00007f8f31447a6e in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#39 0x00007f8f3145cda1 in ?? () from /usr/lib/libgobject-2.0.so.0
#40 0x00007f8f3145e996 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#41 0x00007f8f3145ef53 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#42 0x00007f8f330cae8b in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0
#43 0x00007f8f32f29718 in gtk_dialog_run () from /usr/lib/libgtk-x11-2.0.so.0
#44...

Read more...

Revision history for this message
su_v (suv-lp) wrote :

Which OS/platform are you using, and which Inkscape version?

> I got this stack trace by doing gdb `which inkscape` corefile.

You don't have the debug symbols for Inskcape installed. AFAICT no useful information in the backtrace with regard to where the crash happened in inkscape.

> when using about 7 different layers and trying to cut a
> polygon out of one of them

Do you remember what tools and (menu) commands had been involved? You can't "cut" something out of a layer in Inkscape - did you select two objects from different layers and used 'Path > Cut' or 'Path > Difference'? Are these objects/paths in any way specially complex (like e.g. huge, with many nodes)? Which tool was active when the crash happened (e.g. select tool, node tool)?

Revision history for this message
Tom Dignan (tom-dignan) wrote :

* Kubuntu 10.04 latest
* AMD64

The crash occured when I selected a curved triangle I made, and hit
control + x.
I will try to make it happen again later tonight.

I'll compile the latest with symbols and start working with that one.

Sorry I didn't have more info.

On Wed, Mar 2, 2011 at 12:36 PM, ~suv <email address hidden> wrote:
> Which OS/platform are you using, and which Inkscape version?
>
>> I got this stack trace by doing gdb `which inkscape` corefile.
>
> You don't have the debug symbols for Inskcape installed. AFAICT no
> useful information in the backtrace with regard to where the crash
> happened in inkscape.
>
>> when using about 7 different layers and trying to cut a
>> polygon out of one of them
>
> Do you remember what tools and (menu) commands had been involved? You
> can't "cut" something out of a layer in Inkscape - did you select two
> objects from different layers and used 'Path > Cut' or 'Path >
> Difference'? Are these objects/paths in any way specially complex (like
> e.g. huge, with many nodes)? Which tool was active when the crash
> happened (e.g. select tool, node tool)?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/727815
>
> Title:
>  Inkscape crashed when cutting a polygon from another layer (core dump
>  attached)
>
> Status in Inkscape: A Vector Drawing Tool:
>  Incomplete
>
> Bug description:
>  I was using inkscape to draw a pencil from rectangles that I turned
>  into paths. The steps were long and elaborate, so I don't recall them
>  all. This happened more than once. I am on a 64 bit machine. I turned
>  on core dumps so I could at least provide some useful information. I
>  hope it is enough to diagnose the problem.
>
>  Thanks!
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/inkscape/+bug/727815/+subscribe
>

Revision history for this message
su_v (suv-lp) wrote :

> The crash occured when I selected a curved
> triangle I made, and hit control + x.

Was the select tool or the node tool active when the crash occurred?

If the crash only happens when cutting (possibly mixed with undo) in the node tool context, the issue might be similar to bug #696732 which no longer occurs in 0.48.1 (fixed with bug #622350?).

See also more recent similar report bug #729416 (crash when using Ctrl-X in the node tool context <F2>).

su_v (suv-lp)
Changed in inkscape:
importance: Undecided → High
status: Incomplete → New
Martin Owens (doctormo)
Changed in inkscape:
status: New → Incomplete
Revision history for this message
su_v (suv-lp) wrote :

Closing due to lack of feedback. Available information is not sufficient to further investigate the exact cause of the reported crash. Feel free to reopen if the same crash also occurs with current inkscape versions.

Changed in inkscape:
status: Incomplete → Invalid
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.