crash on 'Objects -> Pattern -> Pattern to Objects'

[Ivan Stankovic]

Load the attached file and then select the 'X' object after the 'test ->' string.
Then click Objects -> Pattern -> Pattern to Objects and Inkscape will crash.

[nightrow (jb-benoit)]

I can't reproduce it on winXP with the Inkscape0801060323.7z build
What version did you made your test on ? (and what platform)

[Ivan Stankovic (ivan-stankovic)]

It's on GNU/Linux, amd64. The version is 0.45.1, built Sep 11 2007

[Ryan Lerch (ryanlerch)]

Can you confirm that this happens with a recent SVN version of inkscape (0.46+devel)?

[Ivan Stankovic (ivan-stankovic)]

Yes, it also happens with the development snapshot 17062.

0x00000000004a60c5 in sp_pattern_painter_free (painter=<value optimized out>)
    at sp-pattern.cpp:803
803 if (pat_i && SP_IS_OBJECT (pat_i) && pattern_hasItemChildren(pat_i)) { // find the first one with item children

[bbyak (buliabyak)]

works for me, linux, amd but not 64, rev 19232

[prkos (prkos)]

No crash on 19186, fedora 8, amd 64

It works but I have to hit Pattern to Object twice to make it happen

[ScislaC (scislac)]

This was filed against a now unsupported version of Inkscape. Given that as well as the lack of people being able to reproduce (including myself on svn r19980) and lack of recent follow-up on this issue, this bug report will be closed. If you still have the issue with the current supported version (Inkscape 0.46 as of my writing this), please feel free to re-open this bug report. If you do re-open it, please include your distro name and version.

[Ivan Stankovic (ivan-stankovic)]

I can still reproduce this on x86-64 (Archlinux) with svn r19980. GDB says:

0x00000000004b5dc1 in sp_pattern_painter_free (painter=<value optimized out>) at sp-pattern.cpp:795
795 if (pat_i && SP_IS_OBJECT (pat_i) && pattern_hasItemChildren(pat_i)) { // find the first one with item children

[ScislaC (scislac)]

Ivan,

Has this happened on their officially packaged versions as well?

[Ivan Stankovic (ivan-stankovic)]

Yes, the official Archlinux package has the same problem (this is all on 64-bit, I haven't tested on x86).

[ScislaC (scislac)]

Ivan,
Are you active at all in any Archlinux forums? Perhaps you could ask if someone else there would be able to reproduce it. At least that way we could get it marked as confirmed in our tracker.

[Ivan Stankovic (ivan-stankovic)]

I've asked on the arch-ports mailing list (I don't use forums) and this is what I've got:

http://archlinux.org/pipermail/arch-ports/2008-October/000733.html
http://archlinux.org/pipermail/arch-ports/2008-October/000734.html

My feeling now is that this bug should probably be closed as invalid, but I'll leave that
up to you.