Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#6 g_strfreev at gstrfuncs.c:2406
#7 g_themed_icon_finalize at gthemedicon.c:188
#9 _gtk_icon_helper_clear at gtkiconhelper.c:49
#10 gtk_cell_renderer_pixbuf_set_property at gtkcellrendererpixbuf.c:374
#11 object_set_property at gobject.c:1358
#12 g_object_set_valist at gobject.c:1953
#13 g_object_set at gobject.c:2059
#14 folder_tree_render_icon at em-folder-tree.c:861
#15 apply_cell_attributes at gtkcellarea.c:1284
#16 g_hash_table_foreach at ghash.c:1526
Created attachment 801364 [details]
Created attachment 801365 [details]
Created attachment 801366 [details]
Created attachment 801367 [details]
Created attachment 801368 [details]
Created attachment 801369 [details]
Created attachment 801370 [details]
Created attachment 801371 [details]
Created attachment 801372 [details]
Created attachment 801373 [details]
Thanks for a bug report. The crash happened due to "double free or corruption (out)", according to the backtrace data, which seems like a memory corruption bug, in a sense of some function the code wrote to memory which it should not (as that 'double free' suggests, the function could even free some data it didn't belong to it, thus the correct free call failed in this way). I cannot tell from the backtrace where exactly this memory corruption happened, neither why, because the backtrace "only" shows where the corruption was detected. I'm afraid I'm not able to do anything with this, unless you've some reproducer or steps/hints for the reproducer.
Created attachment 803557 [details]
I am sure that my memory now is fine
(In reply to Mikhail from comment #12)
> I am sure that my memory now is fine
Yes, I've no doubt, and to be honest, when I speak about "memory corruption", then I do not mean the "hardware memory corruption", but "memory corruption caused by the software", like if the code accesses already freed memory, tries to write to it (possibly overwriting other object which was placed on its place after the first free) and so on. These issues can happen in complex code, and can be caused by many factors.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.