use kill -SIGUSR2 pid to dump traces of active allocations ==9890== Memcheck, a memory error detector ==9890== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==9890== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info ==9890== Command: /usr/lib/libreoffice/program/oosplash --valgrind ==9890== ==9890== Syscall param writev(vector[...]) points to uninitialised byte(s) ==9890== at 0x58FA9BD: ??? (syscall-template.S:84) ==9890== by 0x5DDFF28: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==9890== by 0x5DE031C: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==9890== by 0x5DE03A4: xcb_writev (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==9890== by 0x507948D: _XSend (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==9890== by 0x506E78A: ??? (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==9890== by 0x506DA65: ??? (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==9890== by 0x506E994: XPutImage (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==9890== by 0x10CC73: ??? (in /usr/lib/libreoffice/program/oosplash) ==9890== by 0x10E98F: ??? (in /usr/lib/libreoffice/program/oosplash) ==9890== by 0x10B159: ??? (in /usr/lib/libreoffice/program/oosplash) ==9890== by 0x581D3F0: (below main) (libc-start.c:291) ==9890== Address 0x75893d8 is 40 bytes inside a block of size 16,384 alloc'd ==9890== at 0x4C2EB55: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==9890== by 0x5069662: XOpenDisplay (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==9890== by 0x10C44C: ??? (in /usr/lib/libreoffice/program/oosplash) ==9890== by 0x10E98F: ??? (in /usr/lib/libreoffice/program/oosplash) ==9890== by 0x10B159: ??? (in /usr/lib/libreoffice/program/oosplash) ==9890== by 0x581D3F0: (below main) (libc-start.c:291) ==9890== ==9915== Memcheck, a memory error detector ==9915== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==9915== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info ==9915== Command: /usr/lib/libreoffice/program/javaldx -env:INIFILENAME=vnd.sun.star.pathname:/usr/lib/libreoffice/program/redirectrc ==9915== ==9915== ==9915== HEAP SUMMARY: ==9915== in use at exit: 9,186 bytes in 129 blocks ==9915== total heap usage: 2,089 allocs, 1,960 frees, 547,729 bytes allocated ==9915== ==9915== LEAK SUMMARY: ==9915== definitely lost: 0 bytes in 0 blocks ==9915== indirectly lost: 0 bytes in 0 blocks ==9915== possibly lost: 0 bytes in 0 blocks ==9915== still reachable: 9,186 bytes in 129 blocks ==9915== suppressed: 0 bytes in 0 blocks ==9915== Rerun with --leak-check=full to see details of leaked memory ==9915== ==9915== For counts of detected and suppressed errors, rerun with: -v ==9915== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==9919== Memcheck, a memory error detector ==9919== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==9919== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info ==9919== Command: /usr/lib/libreoffice/program/soffice.bin --valgrind --splash-pipe=5 ==9919== --9919-- WARNING: unhandled amd64-linux syscall: 324 --9919-- You may be able to write your own handler. --9919-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --9919-- Nevertheless we consider this a bug. Please report --9919-- it at http://valgrind.org/support/bug_reports.html. ==9921== Syscall param sendmsg(msg.msg_iov[0]) points to uninitialised byte(s) ==9921== at 0x8B6B1B7: sendmsg (sendmsg.c:28) ==9921== by 0x1A4FA5E6: ??? (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.23) ==9921== by 0x1A4F6438: ??? (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.23) ==9921== by 0x1A48EB0D: ??? (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.23) ==9921== by 0x1B993965: ??? (in /usr/lib/nvidia-370/libnvidia-glcore.so.370.23) ==9921== by 0x1B98C143: ??? (in /usr/lib/nvidia-370/libnvidia-glcore.so.370.23) ==9921== by 0x1B98DD72: ??? (in /usr/lib/nvidia-370/libnvidia-glcore.so.370.23) ==9921== by 0x1B98E537: ??? (in /usr/lib/nvidia-370/libnvidia-glcore.so.370.23) ==9921== by 0x1A4E38D9: ??? (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.23) ==9921== by 0x1B98A707: ??? (in /usr/lib/nvidia-370/libnvidia-glcore.so.370.23) ==9921== by 0x1B98B348: ??? (in /usr/lib/nvidia-370/libnvidia-glcore.so.370.23) ==9921== by 0x1A48EDB5: ??? (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.23) ==9921== by 0x1A4BD302: ??? (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.23) ==9921== by 0x1A4C0666: ??? (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.23) ==9921== by 0x1A4B4CD0: glXCreateContext (in /usr/lib/nvidia-370/libGLX_nvidia.so.370.23) ==9921== by 0xFF2133F: glXCreateContext (in /usr/lib/nvidia-370/libGLX.so.0) ==9921== by 0x7A08217: ??? (in /usr/lib/libreoffice/program/libmergedlo.so) ==9921== by 0x7A084AC: ??? (in /usr/lib/libreoffice/program/libmergedlo.so) ==9921== by 0x6689BD9: soffice_main (in /usr/lib/libreoffice/program/libmergedlo.so) ==9921== by 0x1087AA: ??? (in /usr/lib/libreoffice/program/soffice.bin) ==9921== by 0x8A823F0: (below main) (libc-start.c:291) ==9921== Address 0xffeffedcc is on thread 1's stack ==9921== ==9921== ==9921== HEAP SUMMARY: ==9921== in use at exit: 2,274,581 bytes in 1,513 blocks ==9921== total heap usage: 6,568 allocs, 5,055 frees, 1,751,820,438 bytes allocated ==9921== ==9921== LEAK SUMMARY: ==9921== definitely lost: 0 bytes in 0 blocks ==9921== indirectly lost: 0 bytes in 0 blocks ==9921== possibly lost: 284,195 bytes in 23 blocks ==9921== still reachable: 1,990,386 bytes in 1,490 blocks ==9921== of which reachable via heuristic: ==9921== newarray : 1,552 bytes in 17 blocks ==9921== multipleinheritance: 104 bytes in 1 blocks ==9921== suppressed: 0 bytes in 0 blocks ==9921== Rerun with --leak-check=full to see details of leaked memory ==9921== ==9921== For counts of detected and suppressed errors, rerun with: -v ==9921== Use --track-origins=yes to see where uninitialised values come from ==9921== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) ==9919== Warning: noted but unhandled ioctl 0x30000001 with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== Warning: noted but unhandled ioctl 0x27 with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== Warning: noted but unhandled ioctl 0x7ff with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== Warning: noted but unhandled ioctl 0x25 with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== Warning: noted but unhandled ioctl 0x17 with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== Warning: set address range perms: large range [0x200000000, 0x400000000) (noaccess) ==9919== Warning: set address range perms: large range [0x400000000, 0x600000000) (noaccess) ==9919== Warning: noted but unhandled ioctl 0x19 with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== Warning: noted but unhandled ioctl 0x21 with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== Warning: noted but unhandled ioctl 0x1b with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9963== Memcheck, a memory error detector ==9963== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==9963== Using Valgrind-3.12.0.SVN and LibVEX; rerun with -h for copyright info ==9963== Command: /bin/sh -c paperconf\ 2\>/dev/null ==9963== ==9963== ==9963== HEAP SUMMARY: ==9963== in use at exit: 2,498 bytes in 76 blocks ==9963== total heap usage: 79 allocs, 3 frees, 2,650 bytes allocated ==9963== ==9963== LEAK SUMMARY: ==9963== definitely lost: 0 bytes in 0 blocks ==9963== indirectly lost: 0 bytes in 0 blocks ==9963== possibly lost: 0 bytes in 0 blocks ==9963== still reachable: 2,498 bytes in 76 blocks ==9963== suppressed: 0 bytes in 0 blocks ==9963== Rerun with --leak-check=full to see details of leaked memory ==9963== ==9963== For counts of detected and suppressed errors, rerun with: -v ==9963== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==9919== Warning: noted but unhandled ioctl 0x42 with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== Warning: noted but unhandled ioctl 0x22 with no size/direction hints. ==9919== This could cause spurious value errors to appear. ==9919== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==9919== ==9919== HEAP SUMMARY: ==9919== in use at exit: 18,772,793 bytes in 75,490 blocks ==9919== total heap usage: 12,153,047 allocs, 12,077,557 frees, 1,168,768,671 bytes allocated ==9919== ==9919== LEAK SUMMARY: ==9919== definitely lost: 23,747 bytes in 98 blocks ==9919== indirectly lost: 25,387 bytes in 681 blocks ==9919== possibly lost: 1,317,141 bytes in 1,412 blocks ==9919== still reachable: 17,117,742 bytes in 71,052 blocks ==9919== of which reachable via heuristic: ==9919== length64 : 11,152 bytes in 160 blocks ==9919== newarray : 6,616 bytes in 68 blocks ==9919== multipleinheritance: 52,600 bytes in 200 blocks ==9919== suppressed: 0 bytes in 0 blocks ==9919== Rerun with --leak-check=full to see details of leaked memory ==9919== ==9919== For counts of detected and suppressed errors, rerun with: -v ==9919== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) ==9890== ==9890== HEAP SUMMARY: ==9890== in use at exit: 3,054 bytes in 60 blocks ==9890== total heap usage: 953 allocs, 893 frees, 1,060,599 bytes allocated ==9890== ==9890== LEAK SUMMARY: ==9890== definitely lost: 0 bytes in 0 blocks ==9890== indirectly lost: 0 bytes in 0 blocks ==9890== possibly lost: 0 bytes in 0 blocks ==9890== still reachable: 3,054 bytes in 60 blocks ==9890== suppressed: 0 bytes in 0 blocks ==9890== Rerun with --leak-check=full to see details of leaked memory ==9890== ==9890== For counts of detected and suppressed errors, rerun with: -v ==9890== Use --track-origins=yes to see where uninitialised values come from ==9890== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)