Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Saving to file should take place in a process independent of the GUI|
|Component:||ui||Assignee:||AOO issues mailing list <issues>|
|Status:||UNCONFIRMED ---||QA Contact:|
|Priority:||P3||CC:||elish, issues, oleg.nucer|
|Issue Type:||ENHANCEMENT||Latest Confirmation in:||---|
Description jameshfisher 2009-08-31 19:00:25 UTC
When saving a file (including autosaving), in any of the OpenOffice suite, the GUI is locked until the save is complete. When a user is working on a file that is in a remote location, or in any case has a low data rate connection to the client, it can take many minutes to save (or autosave) a file, during which time the user has to simply do something else. In my case, I am reporting this issue due to problems working on a file that is stored on a samba share on the local network. The file contains images and is several megabytes in size. During heavy network load it can take up to ten minutes before I am allowed to resume editing. However, it is not clear why this should be the case. The GUI should perhaps be locked while the serialized file representation of the document is compiled in memory from the current state of the document. However, the saving of this could and should be done in a separate process, allowing the GUI to be unlocked in the meanwhile for further editing.
Comment 1 mr_smyle 2010-12-07 21:09:10 UTC
Also this is very actual when I test beta versions of OpenOffice with my production documents. Yes, I do this ;-) I Set AutoSave option to 2-3 minutes. I can not edit document until saving process ends on big documents. So editing sometimes is very slow. As proposition. Add additional timer to check user idle period (no mouse, no cursor movements) and start saving without interrupt editing.
Comment 2 oleg.nucer 2015-03-03 08:46:26 UTC
Yes, this is very annoying! Every time I press Ctrl+S the GUI hangs out for few seconds... And it's not depends of document size... Even on a tiny doc file with few hundred words. On my Core i5 with 8 Gb RAM and SSD drive it takes 3 seconds..... Very strange. I already had noticed this bug in 3.x version. Now after update to ver 4.0.1 I feel it even stronger!