https://bugs.freedesktop.org/show_bug.cgi?id=71447
--- Comment #27 from James R Shaw <[email protected]> --- I finally was able to put together a REPRODUCIBLE set of steps to create/cure the problem which should help a programmer propose a workable solution to the problem. I was messing around with my virus scanner and the LO memory settings the other day and was able to get fast menu response and thought I was on to something. Then today I observed the 30-40 second open and 30-40 second close/save. Background My thanks to [email protected] who put me on the right track on where to look. Some of the following commentary may be speculative based upon personal programming experience and a lack of knowledge of what is under the hood in LO. On my libreOffice main screen I have 21 thumbnails of documents I regularly open. ONE of these is a networked document that I open once a week. SOMETIMES the remote machine (a laptop) is OFF. SOMETIMES the remote machine is ON. Symptoms When the machine is OFF LO is unable to reach across the LAN to ping the file and create the thumbnail or otherwise perform behind the scenes preloading of some stuff into cache etc. to speed up anticipated future file operations. LO still appears to attempt to reach out to the file even though the system is offline. I would suspect there is some kind of network timeout that is being tripped that is in the 20-30 second range. So when one attempts to startup LO, It pings all the files and builds the Recent Documents list. When it gets to the networked file that is unavailable (remote system is offline) a network timer is started and the recent file list build is suspended waiting on the network request. When the timeout threshold is reached (~30 seconds), the build resumes and is quickly completed. Test 1 with remote system offline Open let's say a spreadsheet and change one individual cell forcing a save. Close the file and click on the save button. The time to close, save, and get back to the LO main process window is in the ~35 second range. I have been living with this behavior for 7 frustrating months. Test 2 with remote system ONline Turn the remote machine on and wait until you can see the disk where the file is located over the network with Windows Explorer or whatever. Open that spreadsheet again. Time to open ~1 second!!! Change one individual cell forcing a save. Close the file and click on the save button. The time to close, save, and get back to the LO main process is in the amazing ~1 second range. This can get even more fun... Test 3 with remote system taken offline prior to save Open that spreadsheet again and change one individual cell forcing a save. Close the file and BEFORE YOU click on the save button, SHUTDOWN the remote computer. The time to close, save, and get back to the LO main process is back to a dismal 23 seconds im my specific case. I have resorted to using an old copy of MS office when I know that the remote system will be off and the 30 second delays are going to be happening. Proposed solution for the programmer. One may want to add an option or two to steer this behavior--timing parameters and such. Treat all networked files on the most recently used list asynchronously, on the first pass/build--skip them and fill them in on a second pass AFTER the list is built AND displayed. At least two places will have to be treated this way: the File=> Recent Documents pull-down and the main LibreOffice screen with all the thumbnails. I hope this info helps provide a solution... -- 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
