Inkscape crashes when clicking fill/stroke tool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Expired
|
High
|
Unassigned |
Bug Description
Inkscape version: Inkscape 0.47pre4 r22446, built Oct 14 2009
Vanilla version as it came with Ubuntu 9.10 "Karmic".
I have had this problem already for several Ubuntu versions; that's why I don't feel like upgrading again to see whether the latest version works better. The funny thing is that it only happens on one particular (old) account on my computer, even if I delete ~/.inkscape and ~/.config/inkscape. If I log in as a different user, it works without problem. I have no clue what bit of configuration is different between these accounts.
Steps to produce error:
1. Start inkscape.
2. Click the fill/stroke icon (it also happens if you draw/select something first).
3. Inkscape crashes; error messages as below:
** (inkscape:2938): WARNING **: GC Warning: Out of Memory! Returning NIL!
** (inkscape:2938): WARNING **: SPObject:
(above two messages repeated about 30 times)
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
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.
** (inkscape:2968): WARNING **: GC Warning: Out of Memory! Returning NIL!
terminate called recursively
Stack trace:
#0 0x00dc9422 in __kernel_vsyscall ()
#1 0x03b3b4d1 in raise () from /lib/tls/
#2 0x03b3e932 in abort () from /lib/tls/
#3 0x050294df in __gnu_cxx:
#4 0x05027415 in ?? () from /usr/lib/
#5 0x05027452 in std::terminate() () from /usr/lib/
#6 0x05027591 in __cxa_throw () from /usr/lib/
#7 0x0835637d in ?? ()
#8 0x08354738 in ?? ()
#9 0x0834da3b in ?? ()
#10 0x08356289 in ?? ()
#11 0x08354738 in ?? ()
#12 0x0834da3b in ?? ()
#13 0x085a8f16 in ?? ()
#14 0x085a965c in ?? ()
#15 0x085a97da in ?? ()
#16 0x085ab13f in ?? ()
#17 0x08384cbb in ?? ()
#18 0x083850fc in ?? ()
#19 0x083686b5 in ?? ()
#20 0x0836509b in ?? ()
#21 0x08364213 in ?? ()
#22 0x083642b8 in ?? ()
#23 0x0823ddbd in ?? ()
#24 0x0092f9fc in g_cclosure_
#25 0x00922072 in g_closure_invoke () from /usr/lib/
#26 0x009377a8 in ?? () from /usr/lib/
#27 0x00938b2d in g_signal_
#28 0x00938fb6 in g_signal_emit () from /usr/lib/
#29 0x00e2ced5 in ?? () from /usr/lib/
#30 0x00e2eebd in gtk_action_activate () from /usr/lib/
#31 0x00fddc2e in ?? () from /usr/lib/
#32 0x0092f9fc in g_cclosure_
#33 0x00922072 in g_closure_invoke () from /usr/lib/
#34 0x009377a8 in ?? () from /usr/lib/
#35 0x00938b2d in g_signal_
#36 0x00938fb6 in g_signal_emit () from /usr/lib/
#37 0x00e4788a in gtk_button_clicked () from /usr/lib/
#38 0x00e48ea8 in ?? () from /usr/lib/
#39 0x0092f9fc in g_cclosure_
#40 0x009206f9 in ?? () from /usr/lib/
#41 0x00922072 in g_closure_invoke () from /usr/lib/
#42 0x009370b0 in ?? () from /usr/lib/
#43 0x00938b2d in g_signal_
#44 0x00938fb6 in g_signal_emit () from /usr/lib/
#45 0x00e4792a in gtk_button_released () from /usr/lib/
#46 0x00e47963 in ?? () from /usr/lib/
#47 0x00f07474 in ?? () from /usr/lib/
#48 0x009206f9 in ?? () from /usr/lib/
#49 0x00922072 in g_closure_invoke () from /usr/lib/
#50 0x0093749e in ?? () from /usr/lib/
#51 0x009389b8 in g_signal_
#52 0x00938fb6 in g_signal_emit () from /usr/lib/
#53 0x0102395e in ?? () from /usr/lib/
#54 0x00effc20 in gtk_propagate_event () from /usr/lib/
#55 0x00f00ea9 in gtk_main_do_event () from /usr/lib/
#56 0x0051d65a in ?? () from /usr/lib/
#57 0x017f4e88 in g_main_
#58 0x017f8730 in ?? () from /lib/libglib-
#59 0x017f8b9f in g_main_loop_run () from /lib/libglib-
#60 0x00f01419 in gtk_main () from /usr/lib/
#61 0x002dd5e7 in Gtk::Main:
#62 0x002dd3e2 in Gtk::Main::run() () from /usr/lib/
#63 0x0808863b in ?? ()
#64 0x08164f9a in ?? ()
#65 0x08087ac2 in ?? ()
#66 0x03b27b56 in __libc_start_main () from /lib/tls/
#67 0x08086b71 in ?? ()
tags: | added: crash |
Changed in inkscape: | |
importance: | Undecided → High |
Do you still have this issue and is it repeatable? Reading the report, it seems to me that there is a problem with your user configuration ...