Bug 76874 - FILESAVE: Infinite Autosave
Summary: FILESAVE: Infinite Autosave
Status: RESOLVED DUPLICATE of bug 46635
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.2.1 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-01 01:04 UTC by sampitt94
Modified: 2014-08-28 21:43 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sampitt94 2014-04-01 01:04:14 UTC
Problem description: Autosave is set to save every 5 minutes, but when the document is left idling, LO starts to autosave about every five seconds or so - autosaving takes much longer than it probably should and seems to happen multiple times, and sometimes if left long enough, LO will start autosaving infinitely many times, causing you to force the program to close and frequently losing data.

Steps to reproduce:
1. Set autosave to five minutes and "save document too" setting
2. Open new document
3. Make changes
4. Leave LO sitting for a few seconds

Current behavior: Overly frequent autosaving, saving multiple times per autosave, sometimes getting stuck in a loop where it never stops

Expected behavior: Autosaving once every five minutes

              
Operating System: Windows 8
Version: 4.2.2.1 release
Comment 1 Björn Michaelsen 2014-04-01 19:49:44 UTC

*** This bug has been marked as a duplicate of bug 46635 ***
Comment 2 Reinhard Lamsfuss 2014-07-31 08:38:35 UTC
(In reply to comment #1)
> 
> *** This bug has been marked as a duplicate of bug 46635 ***

Yes, but it can be reproduced WITHOUT IMPLYING AUTORECOVERY at all. It is sufficient to have an modified "untitled" open without saving for the loop to get triggered.
Comment 3 Reinhard Lamsfuss 2014-08-28 21:34:44 UTC
Problem persists in Version: 4.3.1.2
Build-ID: 958349dc3b25111dbca392fbc281a05559ef6848
Comment 4 Maxim Monastirsky 2014-08-28 21:43:42 UTC
(In reply to comment #3)
> Problem persists in Version: 4.3.1.2
It was fixed for 4.3.2, see Bug 71625.