Inkscape

inkscape crashed with SIGSEGV

Bug #673986 reported by Brice Terzaghi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Incomplete
Undecided
Unassigned
inkscape (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: inkscape

Inkscape crashed after undoing an operation with ctrl + Z.

Not sure it is related or normal but displaying memory usage (from Inkscape help menu) shows a "standard malloc()" that constantly fluctuates, even when doing nothing. libgc usage doesn't change.

Ubuntu 10.10 with Inkscape 0.48 from the Maverick repo.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: inkscape 0.48.0-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Nov 11 13:12:22 2010
ExecutablePath: /usr/bin/inkscape
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: inkscape
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x47bff8: add -0x18(%rax),%rdi
 PC (0x0047bff8) ok
 source "-0x18(%rax)" (0x206573696c69743d) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: inkscape
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: inkscape crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1672): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (awn-applet:1714): Wnck-CRITICAL **: wnck_workspace_is_virtual: assertion `WNCK_IS_WORKSPACE (space)' failed

Revision history for this message
Brice Terzaghi (terzag) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Inkscape::UI::CurveDragPoint::_getTip (
 Inkscape::UI::ControlPoint::_updateTip (
 Inkscape::UI::ControlPoint::_setMouseover (
 Inkscape::UI::ControlPoint::_eventHandler (
 Inkscape::UI::ControlPoint::_event_handler (

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in inkscape (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Hi Brice,

Thanks for reporting this bug. Have you found a step-by-step method of reproducing the bug or does it seem to happen at random?

visibility: private → public
tags: added: crash undo
removed: maverick
Changed in inkscape (Ubuntu):
status: New → Incomplete
Changed in inkscape:
status: New → Incomplete
Revision history for this message
Brice Terzaghi (terzag) wrote :

No, it seems to be random, although it's not the first time Inkscape crashes on my system when using ctrl + Z (it has happened a few times over the years, with different versions of Inkscape and Ubuntu).

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

Similar to bug #664831 “Undo after drag path causes inkscape to crash”, could be another duplicate of bug #544599 “Node editing causes segmentation fault”.

Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Yes, it's exactly the same backtrace so I think we can safely mark as a duplicate of bug #544599. If we can identify a completely different set of steps for triggering the crash, then we can separate the reports again, I guess.

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

Other bug subscribers

Remote bug watches

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