Total failure - Githubissues

jmcd040 commented 5 years ago

I have numerous files both in the database and on disk. I added a new scratch document with the plus sign, pasted some text into it and later deleted the text. A little while later when I came back to WM3 (without closing it), all my work was gone. My project names were there, but contained no documents. The ALL file selection showed no documents, just several empty SCRATCH documents. I checked the database backup and it matches the current database. So no help there. Somehow the database backup had been cleaned out too. The only other odd thing was that there were several NW.exe tasks running in Windows 10. I don't know how that happened. I had to close all of them using the Windows Task Manager.

I was finally able to recover database backup files that were about 3 hours old from my Windows File History and restore the active database files from there. But that puts me hours behind. I'm on a tight deadline and this was disturbing.

writemonkey commented 5 years ago

Fuf, that sucks. I don't know how is that even possible. WM won't allow multiple instances of the app so multiple nw.exes is also very strange. i.

jmcd040 commented 5 years ago

I later noticed that when WM3 runs, it creates multiple tasks, so maybe it wasn't actually multiple instances. However the program wouldn't close so I had to kill all the tasks one by one in task manager. I wish I had paid attention more to exactly what the steps were I took in all this.

jmcd040 commented 5 years ago

It happened again. I had WM3 save backups several times yesterday. All was working normally. I closed the program last night. This morning there were no files - project definitions and repository were ok but no files. By looking at my Windows File History which backs up every 30 minutes, I found that the writemonkey3_sheets file had vanished sometime yesterday afternoon. Fortunately I was able to find an older backup and WM3 updated my working file from my hard drive to get me back to the latest version.

Backing up the database in WM3 is a nice idea unless the files in <user>/appdata/local/writemonkey 3 become corrupt. Trying to reinstate the "OLDER" versions of the backup seem too time-consuming and error prone. But the main problem seems to be corruption of the main database from time to time. So I need to have all my work linked to hard files. The problem I have with that is if I want to change the name of a file on my disk I have to go through, unlinking, changing the file name and relinking.

jmcd040 commented 5 years ago

Happened again. Was working on several docs. Condensed and backed up the database, but noticed that the menu text indicating the from the last backup wouldn't change. Closed the program. Opened and all the documents were gone. The sheets file was empty. Restored from a backup and decided to dump everything from the database except the file I'm working on and some docs that are not linked to external files that I don't modify often, so I don't care if they are restored from old backups. I don't find this a comforting way to work.

writemonkey commented 5 years ago

Hi Jim, unfortunately you are the only one reporting this. I took some time and tried to corrupt the database by compacting and backuping the db multiple times in fast succession. No corruption at my end.

How big are your db files? writemonkey3_sheets and writemonkey3_sheets_history?
Have you changed the default path for db files?
What is your setting for auto save (auto_save_interval)?
Is keep_document_undo_data set to false?
How big was the last opened file when error occurred? Did you work on any very large documents when this happened?

i.

jmcd040 commented 4 years ago

Size of files: sheets 642kb, sheets-history 212 Mb I set the backup directory, but not the db directory location auto_save_interval is 5 keep_document_undo_data is the default, false My documents aren't large, say 3 to 120Kb backup_database_automatically is set to 1 I have had about 25 documents.

DaceKonn commented 4 years ago

Fuf, that sucks. I don't know how is that even possible. WM won't allow multiple instances of the app so multiple nw.exes is also very strange. i.

Actually it's default:

I'm guessing that's a default nodejs behavior or something - one process for each thread or something? I'm not a nodejs specialist. But that's a default way how the app works.

writemonkey commented 4 years ago

Yes, my bad, on Windows, multiple nw.exes in tasks list are ok. Each process is represented with one nw.exe. There should be 4 of them. i.

writemonkey / wm3

Total failure #308