<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - fileopen: Calc can not open xlsx, consuming tens gigs of RAM (memory leak)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126710#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - fileopen: Calc can not open xlsx, consuming tens gigs of RAM (memory leak)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=126710">bug 126710</a> from <a class="email" href="mailto:lo_bugs@iseries-guru.com" title="Terrence Enger <lo_bugs@iseries-guru.com>"> Terrence Enger</a> <pre>Created <a href="http://bugs.documentfoundation.org/attachment.cgi?id=153762" name="attach_153762" title="bt from one of many allocations of size 0x98">attachment 153762</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=153762&action=edit" title="bt from one of many allocations of size 0x98">[details]</a> bt from one of many allocations of size 0x98 Over the course of about two hours I collected mtrace output from LO opening calc-memory.xls before LO crashed. The mtrace output is 13 GB, some 130 million lines. Toward the end of the trace file, there are millions of pairs of lines like (but with changing, apparently increasing locations allocated) (lines rewrapped): @ /usr/lib/x86_64-linux-gnu/libstdc++.so.6:(_Znwm+0x18) [0x7fac2dc80fd8] + 0x557ef01fdb60 0x98 @ /usr/lib/x86_64-linux-gnu/libstdc++.so.6:(_Znwm+0x18) [0x7fac2dc80fd8] + 0x557ef01fdc10 0x30 with only rare other heap operations. The present attachment is a backtrace from one of the allocations of size 0x98. An allocation of size 0x30 is similar, the location in ScDPResultDimension::AddMember having advanded from dptabres.cxx:3959 to line 3963 and there being 6 more call levels between there and operator new. LibreOffice in this case is a local build of source hash 7dcb5c65, 2019-08-19, configured: CC=ccache /usr/bin/gcc CXX=ccache /usr/bin/g++ CCFLAGS=-Wshadow --with-jdk-home=/usr/lib/jvm/default-java --enable-split-debug --enable-gdb-index --enable-ld=gold --enable-option-checking=fatal #--enable-dbgutil --enable-debug --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src --without-package-format built and running on debian-buster. The installed RAM and swap space allowed LO opening the same file in other tests to grow to 10 or 11 GB before crashing. I am removing keyword wantBacktrace and adding haveBacktrace.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>