After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 584848 - g_value_unset critical in gsf_doc_prop_free
g_value_unset critical in gsf_doc_prop_free
Status: RESOLVED FIXED
Product: libgsf
Classification: Core
Component: General
unspecified
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-06-04 17:21 UTC by sum1
Modified: 2009-06-05 17:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sum1 2009-06-04 17:21:31 UTC 
This report is an offshoot of Bug 577208, comment 2.

Steps to reproduce:
- Download Attachment 131634 [details] (fuzzed .xls file from Bug 577208)
- Import the attachment into Gnumeric
- File > Quit to trigger the critical


Console output (warnings ignored):

GLib-GObject-CRITICAL **: g_value_unset: assertion `G_IS_VALUE (value)' failed


Backtrace:

+ Trace 215862

  • #0 IA__g_return_if_fail_warning
  • #1 IA__g_value_unset
    at /build/buildd/glib2.0-2.20.1/gobject/gvalue.c line 271
  • #2 gsf_doc_prop_free
    at gsf-doc-meta-data.c line 261
  • #3 g_hash_table_remove_all_nodes
    at /build/buildd/glib2.0-2.20.1/glib/ghash.c line 374
  • #4 IA__g_hash_table_remove_all
    at /build/buildd/glib2.0-2.20.1/glib/ghash.c line 1051
  • #5 IA__g_hash_table_destroy
    at /build/buildd/glib2.0-2.20.1/glib/ghash.c line 758
  • #6 gsf_doc_meta_data_finalize
    at gsf-doc-meta-data.c line 46
  • #7 IA__g_object_unref
    at /build/buildd/glib2.0-2.20.1/gobject/gobject.c line 2421
  • #8 go_doc_finalize
    at go-doc.c line 104
  • #9 workbook_finalize
    at workbook.c line 158
  • #10 IA__g_object_unref
    at /build/buildd/glib2.0-2.20.1/gobject/gobject.c line 2421
  • #11 dialog_quit
    at dialog-quit.c line 376
  • #12 cb_file_quit
    at wbc-gtk-actions.c line 308 






Comment 1


Morten Welinder





          2009-06-05 17:25:37 UTC
        



This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.