Description: When I use ExitLibreOffice command on pulldown, the user interface window closes properly, but continuing background processes consume all available memory... as observed using Microsoft Resource Monitor. Sometimes, after a couple minutes, the machine will eventually succeed in closing down all Libre processes... other times the machine hard freezes, not accepting any input. Steps to Reproduce: 1.Calc session w/ 8 column x 8000 row table. 2 hour session occasionally deleting single row at a time. 2.Use pulldown to ExitLibreOffice command. 3. (Look at software environment described below) Actual Results: Interface window closes promptly without issue. Problem is in post-processing stage. As observed on Resource Monitor graphs, memory usage spikes about 7GB indicated before machine freezes. Neither CPU nor Disk usage are particularly heavy. It's memory contention/exhaustion. Expected Results: Postclose processing does not consume all available memory, freezing the machine. Reproducible: Always User Profile Reset: Yes Additional Info: Running on an HP 8530 with 8GB installed memory, 740 GB available disk space. Applications open for my typical work session. LibreCalc. GIMP 2.10 Firefox browser with Fireshot screengrab accessory frequently used while visiting web pages. McAfee AV LiveSafe Win 10 all software at latest release level
I may have discovered what is happening. I work with an .ods file during work session, but need to save a copy as a .csv for post-processing in a Python routine and R. What I have been doing is simply doing a SELECT ALL then COPY of the .ods, then open the .csv file, SELECT ALL, DELETE, then PASTE. This is the end of my session after performing this action, so I immediately ExitLibre. Tonight, I tried simply doing a SAVE AS of the .ods to the .csv file. On close down, I noticed NO memory hit due to soffice. I suggest that Calc doesn't deal well with large objects in its clipboard at shutdown and really struggles to release that allocated memory. A guess though.
Could you please retest your problem from Description in latest LibreOffice 7.2.7 or 7.3.3?
Dear dpkesling, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear dpkesling, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp