inkscape crashed with SIGSEGV in GC_invoke_finalizers()

Bug #277366 reported by RyanO on 2008-10-03
Affects Status Importance Assigned to Milestone
inkscape (Ubuntu)

Bug Description

Binary package hint: inkscape

I am using Ubuntu 8.10 Beta and the version of Inkscape is .0.46-2ubuntu1. I was hoping to get the logo I was making to finish the fill and stroke and so I could save. What happened was the inkscape window went dark so I knew it was either crashing or working on something. I was away from the computer for about 20 minutes and the crash dialogue box pops up saying inkscape crashed.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/inkscape
Package: inkscape 0.46-2ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: inkscape
SourcePackage: inkscape
Title: inkscape crashed with SIGSEGV in GC_invoke_finalizers()
Uname: Linux 2.6.27-4-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

#0 sp_pattern_painter_free (painter=0xc7f4880) at sp-pattern.h:41
 pat_i = (SPPattern *) 0xa7c4470
 pp = (SPPatPainter *) 0xc7f4880
#1 0x080ddddf in sp_painter_free (painter=0xc7f4880) at sp-paint-server.cpp:141
 __PRETTY_FUNCTION__ = "SPPainter* sp_painter_free(SPPainter*)"
#2 0x083851cc in nr_arena_glyphs_group_finalize (object=0xd1653f0) at display/nr-arena-glyphs.cpp:377
No locals.
#3 0x08408067 in finalize_object (base=0xd1653f0) at libnr/nr-object.cpp:179
 tracker = {<Inkscape::Debug::EventTrackerBase> = {_vptr.EventTrackerBase = 0x8688c08,
    _active = true}, <No data fields>}

RyanO (rhino20049) wrote :

StacktraceTop:sp_painter_free (painter=0xc475008) at sp-paint-server.cpp:141
nr_arena_glyphs_group_finalize (object=0xd165540) at display/nr-arena-glyphs.cpp:377
finalize_object (base=0xd165540) at libnr/nr-object.cpp:179
GC_invoke_finalizers () at finalize.c:787
GC_notify_or_invoke_finalizers () at finalize.c:844

Changed in inkscape:
importance: Undecided → Medium
Bryce Harrington (bryce) on 2009-04-08
description: updated
Bryce Harrington (bryce) wrote :

A pre-release of the upcoming Inkscape 0.47 is now available in Ubuntu
Karmic for testing. Because *so* much stuff has changed compared with
the version you reported your bug against, would you mind re-testing
this new version and see if this bug is now resolved?

Karmic Alpha CD ISO images are available at:

If you're not testing Karmic yet, there are .debs of this new Inkscape
for Jaunty, Hardy, and Intrepid here:

You might find further bugs when testing this alpha release. If that is
the case, please file a NEW bug report here:

Thanks ahead of time for your testing efforts, and enjoy the new Inkscape!

Changed in inkscape (Ubuntu):
status: New → Incomplete
Alex Valavanis (valavanisalex) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

RyanO (rhino20049) wrote :

I have kept up to date on what has been happening in this bug as I get emails when someone writes something.
On July 6th I wrote back, but as I can see it did not get posted:

"Unfortunately I have no computer to test it on at the moment. I should have one in about a week."

I do have a computer now that I can use so I will be testing it. I have just installed Inkscape so it may take a while for me to figure out if the bug is still there.

Ryan Orser.

RyanO (rhino20049) wrote :

I have tested the Fill and Stroke which was the problem on Inkscape 0.46. I am running Inkscape 0.47pre0 on Ubuntu 9.04 and there is no problem now. As far as I can see it this bug should be closed.

Alex Valavanis (valavanisalex) wrote :

OK, great to hear that the bug is no longer an issue for you. I'll close the bug, but feel free to reopen it if you experience the same problems again in future.

Changed in inkscape (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers