[Gutsy] Inkscape hangs when exporting drawing to bitmap (PNG)

Bug #174620 reported by Anders Wallenquist
4
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned
inkscape (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: inkscape

Inkscape hangs when exporting drawing to bitmap (PNG), this is similar to #162258 but includes Ubuntu 7.10 (Inkscape 0.45.1-1ubuntu build sep 2007).

1) Create a new page, you may add one or more vector objects
2) Export this page to PNG
3) Inkscape will hang or dump

Revision history for this message
wolfger (wolfger) wrote :

I am unable to duplicate on 7.10 with Inkscape 0.45. Are you running 32-bit or 64-bit? Can you give detailed info on how to reproduce the issue?

Changed in inkscape:
status: New → Incomplete
Revision history for this message
Anders Wallenquist (aw) wrote :

I have this problem on AMD single core, AMD dual core, Intel single core, Intel dual core. I believe it's mostly 32-bit Ubuntu installed on these boxes.

From a Mac Mini Dual Core with Ubuntu 7.10 32-bit:

aw@macken:~$ dpkg -l inkscape
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Namn Version Beskrivning
+++-==============-==============-============================================
ii inkscape 0.45.1-1ubuntu vector-based drawing program
aw@macken:~$ uname -a
Linux macken 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
aw@macken:~$

This is the message after an export of a page with a single object (it hangs until I do xkill):

aw@macken:~$ inkscape

Emergency save activated!

Emergency save document locations:
  Nytt dokument 1.2007_12_07_13_45_08.0
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
Segmenteringsfel (core dumped)
aw@macken:~$

This is the message after an export of a blank page (this one does a core dump without a xkill):

aw@macken:~$ inkscape

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
Segmenteringsfel (core dumped)
aw@macken:~$

do you have any use for the core-file? (I dont know where Inkscape puts the file)

Anders Wallenquist (aw)
description: updated
Revision history for this message
Anders Wallenquist (aw) wrote :
description: updated
Revision history for this message
Anders Wallenquist (aw) wrote :

On an AMD single core Ubuntu 7.10

aw@bibliotek:~$ uname -a
Linux bibliotek 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
aw@bibliotek:~$

aw@bibliotek:~$ strace -oinkscape.strace inkscape

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
aw@bibliotek:~$

Revision history for this message
wolfger (wolfger) wrote :

wolfger@bravo:~$ uname -a
Linux bravo 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

I am still unable to see the bug myself, but I think you've given enough information that we can definitely say a problem exists. I'm on KDE, for whatever that's worth.

Changed in inkscape:
status: Incomplete → Confirmed
Revision history for this message
Toma (tomhaste) wrote : Re: [Bug 174620] Re: [Gutsy] Inkscape hangs when exporting drawing to bitmap (PNG)

I get a hang here too. Tho, if left long enough you see that its
simply rendering your SVG into a bitmap. You can reproduce it simply
by making a 2000x2000 page, add alot of detail to it, then try to
render it at 2000x2000 pixels. I think its more an issue of simply not
updating the status bar when exporting.

Revision history for this message
John Cliff (johncliff) wrote :

0.45 could take extremely long to render larger pngs. SVN has had some major fixes wrt this.

Revision history for this message
Anders Wallenquist (aw) wrote :

I have a crash with this blank/empty page. Its the standard size.

Revision history for this message
Anders Wallenquist (aw) wrote :

Makeing the report bug #174872 to the upstream project make this bug-report invisible in Ubuntu bugreports. Is this the correct procedure?

If this is an Ubuntu issue this will never be found. In the upstream project this bug is marked as "invalid", but still I have this problem at least five Ubuntu-boxes i have investigated this on until now. Upstream they want me to use a version of Inkscape that is not even released for Hardy, and if this is the solution then the Ubuntu package maintainer would upgrade too.

It would make more sence if it was duplicated an Ubuntu bug.

Revision history for this message
tedeskar (edeskar) wrote :

I have the same problem on (32-bit Gutsy on a single core AMD) but I don't have more skills than posting my gdb-log for the crash. Hopefully it could be useful:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1231313216 (LWP 7092)]
0xb6c2155b in strlen () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt
#0 0xb6c2155b in strlen () from /lib/tls/i686/cmov/libc.so.6
#1 0xb6bf1de0 in vfprintf () from /lib/tls/i686/cmov/libc.so.6
#2 0xb6c11bdc in vasprintf () from /lib/tls/i686/cmov/libc.so.6
#3 0xb724d317 in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#4 0xb723e1e6 in g_strdup_vprintf () from /usr/lib/libglib-2.0.so.0
#5 0xb723e20b in g_strdup_printf () from /usr/lib/libglib-2.0.so.0
#6 0x081e650f in ?? ()
#7 0xb74aac09 in g_cclosure_marshal_VOID__VOID ()
   from /usr/lib/libgobject-2.0.so.0
#8 0xb749d772 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#9 0xb74ae323 in ?? () from /usr/lib/libgobject-2.0.so.0
#10 0x0a216a48 in ?? ()
#11 0x00000000 in ?? ()

Best Regards/ Tommy

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.