https://bugs.freedesktop.org/show_bug.cgi?id=79979
--- Comment #5 from Michael Meeks <[email protected]> --- Just ran the test under valgrind: $ make CppunitTest_sw_ooxmlexport ... tableCurrupt.docx,12967 File tested,Execution Time (ms) ==12454== ==12454== Valgrind's memory management: out of memory: ==12454== newSuperblock's request for 1048576 bytes failed. ==12454== 2985897984 bytes have already been allocated. ==12454== Valgrind cannot continue. Sorry. ==12454== ==12454== There are several possible reasons for this. ==12454== - You have some kind of memory limit in place. Look at the ==12454== output of 'ulimit -a'. Is there a limit on the size of ==12454== virtual memory or address space? ==12454== - You have run out of swap space. ==12454== - Valgrind has a bug. If you think this is the case or you are ==12454== not sure, please let us know and we'll try to fix it. ==12454== Please note that programs can take substantially more memory than ==12454== normal when running under Valgrind tools, eg. up to twice or ==12454== more, depending on the tool. On a 64-bit machine, Valgrind ==12454== should be able to make use of up 32GB memory. On a 32-bit ==12454== machine, Valgrind should be able to use all the memory available ==12454== to a single process, up to 4GB if that's how you have your ==12454== kernel configured. Most 32-bit Linux setups allow a maximum of ==12454== 3GB per process. ==12454== ==12454== Whatever the reason, Valgrind cannot continue. Sorry. Hah =) so ... I guess I'm out of memory there (at least when running under valgrind). I'm using a 32bit system, which is (perhaps) somewhat unusual - though - quite what is going on I've no idea; perhaps we have an aggressive new leak somewhere. I imagine memory problems bite windows rather earlier at 2Gb ... -- 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
