https://bugs.freedesktop.org/show_bug.cgi?id=54827
Michael Meeks <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #7 from Michael Meeks <[email protected]> --- All the valgrind badness shows things like this: ==17534== Invalid read of size 8 ==17534== at 0x5BB801F: wcslen (wcslen.S:48) ==17534== by 0x5BC13FE: wcsxfrm_l (strxfrm_l.c:107) ==17534== by 0x161F07BE: g_utf8_collate_key (gunicollate.c:399) ==17534== by 0x161F0A0F: g_utf8_collate_key_for_filename (gunicollate.c:671) ==17534== by 0x142F274D: file_system_model_set (gtkfilechooserdefault.c:6645) ==17534== by 0x14309258: _gtk_file_system_model_get_value (gtkfilesystemmodel.c:1606) ==17534== by 0x142F7CFF: name_sort_func (gtkfilechooserdefault.c:6045) ==17534== by 0x1430732F: compare_array_element (gtkfilesystemmodel.c:697) ==17534== by 0x161D4283: msort_with_tmp (gqsort.c:154) ==17534== by 0x161D3FF3: msort_with_tmp (gqsort.c:87) ==17534== by 0x161D4003: msort_with_tmp (gqsort.c:88) ==17534== by 0x161D3FF3: msort_with_tmp (gqsort.c:87) ==17534== Address 0x215ec818 is 40 bytes inside a block of size 44 alloc'd ==17534== at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==17534== by 0x161CCA78: g_malloc (gmem.c:159) ==17534== by 0x161F1381: _g_utf8_normalize_wc (gunidecomp.c:398) ==17534== by 0x161F078A: g_utf8_collate_key (gunicollate.c:395) ==17534== by 0x161F0A0F: g_utf8_collate_key_for_filename (gunicollate.c:671) ==17534== by 0x142F274D: file_system_model_set (gtkfilechooserdefault.c:6645) ==17534== by 0x14309258: _gtk_file_system_model_get_value (gtkfilesystemmodel.c:1606) ==17534== by 0x142F7CFF: name_sort_func (gtkfilechooserdefault.c:6045) ==17534== by 0x1430732F: compare_array_element (gtkfilesystemmodel.c:697) ==17534== by 0x161D4283: msort_with_tmp (gqsort.c:154) Which are in the gtk+ file-selector. I guess this is a memory corruption there; though you'd prolly need to get more callers to get something helpful: re-running valgrind (sorry it's slow) with --num-callers=40 or somesuch would prolly give a more helpful trace. I see file-selector related crashes too from time to time but relatively few. Bjoern - I guess it's a generic Ubuntu bug we can't switch across. Mas - can you confirm you have the same problems in file-roller or gedit or whatever ? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
