Created attachment 6230 backtraces This is the bug I was hunting before bug 11849 hit me. I've only today had the time to do some investigation. I'm getting random segfaults in some of my Thunar windows. They are just idling when they suddenly disappear. I can sort-of reproduce it (takes a while) when I let Thunar idle in /tmp (which is mounted as tmpfs, if that's relevant) There is also bug 10596, which might be the same bug. If you think 10596 should be the place to discuss this, feel free to reopen it and mark this one as a dupe. I've attached three backtraces.
I am not sure, but from your backtraces it looks like the same as 10596. I will resolve this one as duplicate and reopen the original. You might want to add your mail address to CC there. I haven't experienced this yet, and it looks like it will be hard to trace. But as some comments in 10596 state, this seems like some sort of memory corruption (trying to access already freed variables etc., or maybe some loop that causes the stack to explode). Without steps to reproduce, I do not know how to track this. So, some suggestions... 1) Which glib version do you use? For comparison, I have installed 2.42.2 here. Do you see any suspicious rise in memory consumption when this happens? 2) What could help is if you added debugging statements in thunar-file.c, like: http://git.xfce.org/xfce/thunar/tree/thunar/thunar-file.c#n651 gchar *p = g_file_get_path (path); g_print ("thunar_file_monitor_update: %s\n", p); g_free (p); To the beginning of the function. Similar to the folder monitor function: http://git.xfce.org/xfce/thunar/tree/thunar/thunar-folder.c#n706 Of course, do not forget to free the gchar variable or it will be a source of a leak itself. With these in place, you might get a starting point to trace it. 3) Since you seem to be able to reproduce it, bisecting this to determine the first bad commit could help with finding the cause(s). If you have never done this, searching for "git bisect" will certainly turn up lots of tutorials. Using "DESTDIR=/install/dir/of/your/choice make install" and launching thunar from there will make this easy, just don't forget to kill any running thunar daemon. *** This bug has been marked as a duplicate of bug 10596 ***