Crash with SVG file created few months ago in Inkscape

[Adrian]

OS: Ubuntu 13.10
Inkscape version: Inkscape 0.48+devel r

I fail to open SVG file created few months ago with Inkscape.
The binary comes from http://ppa.launchpad.net/inkscape.dev/trunk/ubuntu

I'm attaching the file causing issue.

Output from gdb (unfortunately, the biary doesn't contain debug symbols...):
#0 0x000000000059672e in ?? ()
#1 0x000000000056cff4 in ?? ()
#2 0x000000000056e408 in ?? ()
#3 0x000000000059591f in ?? ()
#4 0x00000000005772e7 in ?? ()
#5 0x00000000005a4374 in ?? ()
#6 0x000000000059591f in ?? ()
#7 0x00000000004a7c93 in ?? ()
#8 0x00000000004a7cb9 in ?? ()
#9 0x00007ffff12303b6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ffff1230708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff1230b0a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff6956f62 in gtk_dialog_run () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x000000000086c80d in ?? ()
#14 0x00000000004c461c in ?? ()
#15 0x00000000006e5db2 in ?? ()
#16 0x00007ffff14f9188 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007ffff150ab1d in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x00007ffff1512829 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007ffff1512ae2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007fffef8e7ca8 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#21 0x00007fffef906b11 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#22 0x00007ffff12303b6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007ffff1230708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007ffff1230b0a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007ffff69ca277 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#26 0x0000000000475a0c in ?? ()
#27 0x00007ffff0406de5 in __libc_start_main (main=0x459c00, argc=1, ubp_av=0x7fffffffdfa8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdf98) at libc-start.c:260
#28 0x000000000047230f in ?? ()

Regards,
Adrian

[Alvin Penner (apenner)]

confirmed on Windows XP, Inkscape rev 12976

received 19 console messages of the type:

WARNING: Requested update while update in progress, counter = 6

Emergency save activated!

[Alvin Penner (apenner)]

the above 19 messages may have been misleading, attached is a backtrace:

C:\InkscapeBZR\inkscape>gdb inkscape
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-mingw32"...
(no debugging symbols found)
(gdb) symbol-file inkscape.dbg
Reading symbols from C:\InkscapeBZR\inkscape/inkscape.dbg...done.
(gdb) run
Starting program: C:\InkscapeBZR\inkscape/inkscape.exe
[New thread 3620.0xe28]
[New thread 3620.0xe30]
[New thread 3620.0x650]
[New thread 3620.0xdb8]
[New thread 3620.0xef0]
[New thread 3620.0xee4]
[New thread 3620.0xee0]
[New thread 3620.0xedc]
warning: Lowest section in C:\WINDOWS\system32\xpsp2res.dll is .rsrc at 00011000

[New thread 3620.0xee8]

Program received signal SIGSEGV, Segmentation fault.
0x004d3a64 in Inkscape::Pixbuf::create_from_data_uri ()
(gdb) bt
#0 0x004d3a64 in Inkscape::Pixbuf::create_from_data_uri ()
#1 0x07f440f0 in ?? ()
#2 0xffffffff in ?? ()
#3 0x00000000 in ?? ()
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x004d3a64 in Inkscape::Pixbuf::create_from_data_uri ()
(gdb) c
Continuing.

Program exited with code 030000000005.
(gdb) q

C:\InkscapeBZR\inkscape>

[su_v (suv-lp)]

> confirmed on Windows XP, Inkscape rev 12976
> #0 0x004d3a64 in Inkscape::Pixbuf::create_from_data_uri ()

Duplicate of bug #1273244? (see last comment there).

With newer builds (rev >= 12978), it crashes due to bug #1272649:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0x0000000000000000
0x0000000100123ac6 in SPObject::detach ()

[su_v (suv-lp)]

> confirmed on Windows XP, Inkscape rev 12976
>
> received 19 console messages of the type:
>
> WARNING: Requested update while update in progress, counter = 6

This probably indicates that bug #1273900 is about the same issue (crash on load with missing linked bitmap image)?

[su_v (suv-lp)]

On OS X 10.7.5, same results as in bug #1273244?:
- not reproduced with rev <= 12953
- reproduced with rev >= 12954:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x00000001001820bf in Inkscape::Pixbuf::create_from_data_uri ()

- reproduced with rev >= 12978:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0x0000000000000000
0x0000000100123ac6 in SPObject::detach ()

[su_v (suv-lp)]

Proposing to link as duplicate to bug #1273244.

[su_v (suv-lp)]

@Adrian - does the bitmap image 'systemArch.png' exist on your system?
Inkscape tries to load it from the same directory as the SVG file, and if that fails, attempts the path stored in the 'sodipodi:absref' attribute of the <image> element.

[Adrian (adrianf0)]

@SUV - Even with the systemArch.png in the proper directory, Inskscape crashes. Moreover, the bitmaps should be "embedded" in the file. I was not using links. In fact, one can see that they are there, if opens the file in a web browser.

[su_v (suv-lp)]

@Adrian - yes, it is expected that with rev >= 12978 inkscape-trunk crashes, whether the linked bitmap image is present or not. I asked because I wanted to clarify what triggered the originally reported issue here (there had been two separate recent regressions wrt to bitmap images, and your report doesn't include revision information).

Thanks for the feedback - linking as duplicate to bug #1272649.

> Moreover, the bitmaps should be "embedded" in the file.

If you think that Inkscape either ignored your actual import settings for bitmap images for one import, or extracted & linked an embedded bitmap image without being explicitly told to do so, please file a separate report, with steps to reproduce.