https://bugs.documentfoundation.org/show_bug.cgi?id=157912
Steven Casey <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #16 from Steven Casey <[email protected]> --- To add some more info to this report from some things I noticed while attempting a bibisect: I get a "general input/output error" while attempting to bibisect using win32-5.0 repo and get an instant crash while using repo win32-6.1. I suspect this error has to do with 32bit vs 64bit memory constraints which is why this error doesn't happen in the 64bit versions. That is just a wild guess though. It does open while using the win64-7.0 repo albeit pretty slow and jumping to 11GB RAM usage while loading on the master build. Weirdly enough, using the oldest build on win64-7.0 results in half the RAM being used when loading. Hitting a max of 5.5GB and usually sitting around 4.8GB on my system. The commit that causes it to double is commit 5dca5309207b6b3cd5bed68da47223e08a3ac3f8 (win64-7.0 repo) but I am definitely not comfortable formally blaming this commit as the cause, especially since this issue seems larger. Also, it looks like when using the win64-6.4 repo, the master and the oldest both have high RAM usage (~11GB) which leads me to believe the low memory usage in win64-7.0 was a coincidence or related to something else. Regardless, scrolling causes massive lag and RAM usage on all of the versions I have tested. While opening on a newer version of LO I can observe LO using up to 15GB of RAM while opening the pdf which is worse than on the 7.0 master version. While scrolling I observed LO using a whopping 24GB of RAM before ultimately crashing. That is on this version: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 32; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded My system is using 32GB RAM for all of these tests. Hopefully someone with better bibisecting experience can pinpoint the cause and issue :) -- You are receiving this mail because: You are the assignee for the bug.
