Lovely - thanks so much for that Julien - very helpful. You can see the mess that Java makes in the trace (be nice to turn that off somehow I guess if it's possible). Sadly the Python garbage collector also produces a huge mass of false positives as well [ I guess disabling / deleting *py*.so in program/ might help ;-].
Seemingly the trace also doesn't show the crash - did you manage to get it to crash under valgrind ? it seems like the attached trace stops in the middle somehow (which is odd). I'd expect the trace to end: ==13539== ==13539== HEAP SUMMARY: ==13539== in use at exit: 64,093 bytes in 342 blocks ==13539== total heap usage: 764 allocs, 422 frees, 154,216 bytes allocated and some more lines :-) Any chance you can re-try having disabled java and clobbered python ? :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/785518 Title: [Upstream] soffice.bin crashed with SIGSEGV in SdrEndTextEdit() To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/785518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
