<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - FILESAVE: Auto save timing logic problem: can save too frequently" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122530#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - FILESAVE: Auto save timing logic problem: can save too frequently" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122530">bug 122530</a> from <a class="email" href="mailto:luke.kendall@gmail.com" title="Luke Kendall <luke.kendall@gmail.com>"> Luke Kendall</a> <pre>Created <a href="http://bugs.documentfoundation.org/attachment.cgi?id=151613" name="attach_151613" title="Two longish documents">attachment 151613</a> <a href="http://bugs.documentfoundation.org/attachment.cgi?id=151613&action=edit" title="Two longish documents">[details]</a> Two longish documents The documents I wanted to include have a lot of comments, but I can't get Writer to display the document(s). 6.2.3.2 just goes to 90-100% CPU and stays there. I'll give it an hour and see if it loads within that time, but I'm not optimistic. I can't provide that document without obfuscating it, however. All the same, here are two obfuscated documents that take a reasonable length of time to save. If you're willing to take a suggestion, I think it may be easier to find the bug by looking at the logic of the existing code and asking "How is it possible for an auto-save to start, for a document, only minutes after it has been manually saved and the auto-save period is set to 30 mins?" If the logic for auto-save for the current document includes the test "if Now - current_doc.save_instant < autosave_period then {don't save}", it simply should never be possible. (PS: 15mins later, other .odt file still not displaying, soffice 80-100% CPU)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>