GNOME Bugzilla – Bug 666158
crash wrt. filesystem model
Last modified: 2012-11-02 04:36:52 UTC
I run Evolution for a day; I routinely save attachments in /tmp - I have no file selectors lingering left open - but still my evolution process grinds to a near halt whenever I do a compile: [ which creates then deletes lots of files in /tmp very quickly ]. I assume this is down to the leakage / non-destruction of some file-selector model, that is perhaps even a 'feature' ? :-) anyhow, by now I'm used to suspending my build and waiting for evolution to come back when I want to read mail, and magic like: 'sleep 60; fg' in the build terminal to try to remember to keep that thing going. But I digress. Having updated to gtk+ 3.2 (from 3.0 - though this issue has been there ~forever) - I now get a crash: Program received signal SIGABRT, Aborted. 0xb75928c5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) bt
+ Trace 229273
$1 = {parent_instance = {g_type_instance = {g_class = 0xd2763d0}, ref_count = 2, qdata = 0x19b0e4b0}, dir = 0x136d9550, dir_thaw_source = 0, attributes = 0x1f696a08 "standard::name,standard::type,standard::display-name,standard::is-hidden,standard::is-backup,standard::size,standard::content-type,time::modified", dir_monitor = 0x1830f0f0, cancellable = 0x19b35560, files = 0x1828a550, node_size = 216, n_nodes_valid = 0, file_lookup = 0x19a8da38Traceback (most recent call last): File "/usr/share/glib-2.0/gdb/glib.py", line 123, in children return self._iterator(self.val, self.keys_are_strings) File "/usr/share/glib-2.0/gdb/glib.py", line 79, in __init__ self.array = ht["nodes"] gdb.error: There is no member named nodes. , n_columns = 10, column_types = 0x226474f0, get_func = 0xb7a656b0 <file_system_model_set>, get_data = 0xa3709f8, filter = 0x0, sort_column_id = 0, sort_order = GTK_SORT_ASCENDING, sort_list = 0x22371d50 = {0x13723770, 0x170479c0, 0x144e3370, 0x17047850, 0x16ff87a0, 0x14af5b50, 0x17047870, 0x8f55bb0, 0x16ff89b0, 0x1812d580}, default_sort_func = 0, default_sort_data = 0x0, default_sort_destroy = 0, frozen = 0, filter_on_thaw = 0, sort_on_thaw = 0, show_hidden = 0, show_folders = 1, show_files = 1} Why we have this sorted file system model lingering about - I have no idea :-)
*** Bug 661773 has been marked as a duplicate of this bug. ***
bug #653038 is prolly a duplicate.
*** This bug has been marked as a duplicate of bug 687196 ***