[Libreoffice-bugs] [Bug 53154] Closing Report Wizard crashes LibreOffice

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Aug 7 13:24:44 CEST 2012


https://bugs.freedesktop.org/show_bug.cgi?id=53154

--- Comment #13 from Michael Meeks <michael.meeks at novell.com> 2012-08-07 11:24:44 UTC ---
We need to run under valgrind, ignore the python GC thrash, and find out where
this memory corruption comes from:

#14 0x00007f0a60de4b70 in malloc_printerr (action=2, str=0x7f0a60ebb930
"free(): corrupted unsorted chunks", ptr=

The "do all sorts of crazy stuff from a signal handler" approach we have to
these faults is a best-effort attempt to handle simple crashes, and - well - as
you see it is rather flawed. Doing better is rather hard - particularly around
mutex states.

We could try to do some heavy-duty poking / resetting of mutex state as we
catch the signal somehow I guess; but that's hard for the internal libc
protections :-)

Best to find / fix the underlying memory corruption I guess; for that valgrind
is our friend.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Libreoffice-bugs mailing list