Inkscape on Ubuntu crashes with identical process...

Bug #1301076 reported by William Holt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
High
Unassigned

Bug Description

I converted a text object(with fill and stroke[1.75px]), and a linked offset(with fill, blur[2.1], rounded joins&caps, xml radius[3]) to paths, combined the paths in 2 pieces (original text paths, offset paths), then grouped the 2 pieces, centered it vertically and horizontally [ctl+shft+A] after selecting 2 pieces and background polygon shape(with fill and stroke) [alt+shft+left click]. I then selected the offset with the point selector and tried to adjust the blur at which point it crashed, I have duplicated this process repeatedly...

Inkscape version (taken from attached SVG file):
   inkscape:version="0.48.3.1 r9886"

Revision history for this message
William Holt (6-bill-u) wrote :

this is the file that crashes the step is always the same...

su_v (suv-lp)
description: updated
tags: added: crash
removed: object path to
Changed in inkscape:
importance: Undecided → High
Revision history for this message
su_v (suv-lp) wrote :

Crash reproduced with 0.48.3.1 and 0.48+devel r13248 on OS X 10.7.5 (using the attached emergency-saved file, and blurring the object with id 'register_glow'):

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000010
0x000000010004cbd5 in modify_filter_gaussian_blur_from_item ()

tags: added: filters-svg
Changed in inkscape:
status: New → Confirmed
Revision history for this message
su_v (suv-lp) wrote :
Revision history for this message
su_v (suv-lp) wrote :

The bug description and steps to reproduce seem to omit basic information: the SVG file in question seems to have been handed-edited (or modified with a custom extension or an external application) - the trigger for the crash AFAICT is related to the internal stylesheet, which defines a custom style for the path with id 'register_glow' which references a filter effect not present in the file:

#register_glow{fill:#d62f1f;fill-opacity:1;stroke:none;filter:url(#filter4815);}

If that filter definition is present - e.g. by adding one with the same id to the <defs> section - the crash does not occur when changing the blur via 'Fill and Stroke' dialog:
<filter
     color-interpolation-filters="sRGB"
     id="filter4815"><feGaussianBlur
       id="feGaussianBlur9999"
       stdDeviation="1.0" /></filter>

Could you share the steps how the internal style sheet is created, and kept up-to-date with the properties in the style attributes of the individual objects?

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

Simplified test case attached

Steps to reproduce the crash:
1) launch with current trunk
2) open attached file
3) 'Edit > Find' -> search for 'register_glow' in 'Properties'
4) open Fill&Stroke, blur selected object
--> crash

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

Simplified test case attached which has missing filter definition added: no crash with same steps.

su_v (suv-lp)
tags: added: css
Revision history for this message
Johan Engelen (johanengelen) wrote :

somewhat fixed in rev. 13266.
we should keep this bugreport open i think.

Revision history for this message
Nathan Lee (nathan.lee) wrote :

Looks completely fixed by your fix johanengelen. Is there a specific issue this bug should focus on now? (perhaps it's only been fully fixed in 1.0, which is what I've tested on)

Otherwise I'd vote to close (well, as part of bug migration to GitLab, we would close this issue and open new issues in inbox anyhow https://alpha.inkscape.org/bug-migration/)

Max Gaukler (mgmax)
Changed in inkscape:
status: Confirmed → Incomplete
Revision history for this message
Qantas94Heavy (qantas94heavy) wrote :

Closing, if this is still an issue please file a new bug report at https://inkscape.org/inbox.

Closed by: https://gitlab.com/Qantas94Heavy

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