https://bugs.documentfoundation.org/show_bug.cgi?id=160384
--- Comment #10 from Tom Atkinson <[email protected]> --- (In reply to m_a_riosv from comment #4) > In your sample file, takes a few seconds, less than ten to load, and about > forty seconds to recalculate the page's number with: > Version: 24.2.2.2 (X86_64) / LibreOffice Community > Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 > CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win > Locale: es-ES (es_ES); UI: en-US Calc: CL threaded > > The document is plenty of direct format, for both paragraph and character, > and with a large table across several pages at the end. > Seems the main issue is about recalculate pages number. > Disabling automatic spellcheck, helps to move through the document. > Maybe there is some option for paragraphs or tables, making it difficult to > establish the pages. For people who have confidential / sensitive data, is there a logging option I can turn on at the command-line? On a recent editing session: libreoffice /home/tom/Dropbox/Astonishing-Evidence-of-Life/An-Astonishing-MASTER.odt libpng warning: iCCP: extra compressed data libpng warning: iCCP: extra compressed data qt.qpa.clipboard: QXcbClipboard: Cannot transfer data, no data available qt.qpa.clipboard: QXcbClipboard: Cannot transfer data, no data available kf.kio.filewidgets.kfilefiltercombo: Could not find filter "*.odg|ODF Drawing (.odg) " libpng warning: iCCP: extra compressed data libpng warning: iCCP: extra compressed data libpng warning: iCCP: extra compressed data libpng warning: iCCP: extra compressed data I just noticed this is marked as resolved? I will post my fix idea in a new feature request. The fix is: 1. Put autosave on background thread, cease using file locks or locking the interface (during autosave but not save). I still can't use Save but at least I can work on the file 60 seconds of each minute now. 2. Using an IPC interupt such as a boolean flat like #UPDATE that signals a need to cancel any running backing threaded "autosave" (not save) as soon as the user begins interacting again (monitor keyboard mouse for any keystrokes) that eventually stops the autosave thread inside of 1 second so deep inside a huge loop I guess. Meanings, if the user begins typing and changing the file (actually even just scrolling is blocked during autosave). He needs to see a flashing cursor, not a pale white screen every 31 seconds (like I have it presently for laffs). I will now go and change my autosave to.... back to 10 minutes. Now I now why it was set at 10 before. I just tried 1 minute but could not work the file 51% of the time. I will re-post this text to a new feature request now. -- You are receiving this mail because: You are the assignee for the bug.
