-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Crash erased bibliography file #11454
Comments
Seems very similar to #10853 . Though what causes the crash is still a mystery to me (kinda occurs at random, and I haven't found one way to reproduce the bug 100% reliably) |
Did you install the arm version? Jabref also regularly creates backup https://docs.jabref.org/advanced/autosave See the section on where to find the backup. |
The mac crash report could be a parsing error from the 0kb file that Java cannot read the file |
I had a similar situation on version 5.12 some time ago. At that moment the program simply froze and quit. After restarting the program, it offered to restore the latest data and after loading the library was empty. I had made a backup a few weeks before, so I wasn't too upset. This was on Linux Ubuntu 22.04. |
JabRef saves the library now and then. See https://docs.jabref.org/advanced/autosave for details. I would be curious if these files contain data or if all of them are 0 bytes |
The issue is that the backup is here and complete but the file opening fails anyway so jabref just rewrite with nothing |
I think, I understand correctly that the backup file cannot be loaded. Can you share that backup file @Doublonmousse? You find my email address on my GitHub profile. |
Hello, I did not indicate in the bug report what the backup file's name was when the crash occured so finding it back (when there isn't an obvious 0kb file somewhere) is a little bit meh.. Not sure I have it. The thing is, back on 5.12, a force quit would not trigger the issue but having a segfault (with the mac os report about an error popping up) would. So I was trying to see if triggering a segfault on purpose would recreate the same situation or not. For now I'm unsuccessful. Although one thing about 5.15 is that unsaved documents aren't backed up (there isn't anymore a temp save in that situation). That seems like a regression from 5.12 (and I wanted to try that as that was one of the setup for which I had some odds of the situation occuring). Maybe I'll re test this on older versions (5.12 or 5.13) |
What do you mean? Like "unnamed library" if you create a new one? Or while you are working on it? The directories where these backup files reside were described by Thilo at https://discourse.jabref.org/t/references-suddenly-wiped-urgent/4407/2?u=koppor. I need to check if we are saving during editing, but I would say: yes - because I constantly get "backup existing" messages when I "play around" with JabRef. |
Idea to improve user experience
Alternative: Switch to git for backup (refs https://github.com/koppor/jabref/issues/578) - or switch to RCS for backup. Update: We should support "squashing" history - so that for one year ago, thre is only one version, not several. According to so, git-bundle is a nice option to have one file storing the history. - see https://embeddedartistry.com/fieldatlas/git-bundle-workflow/ for some inspiration. If jgit supports git-bundle as remote, we could store the bundle in the directory of the bib file - and clone into TEMP on each open of the library. Save on TEMP dir, commit and push. |
It happened again to me, no idea why it crashed (I was writing a comment on an entry) but the library file was still there and only emptied when I tried to restore. I can send the backup file over email. I have indeed started GitHub backups after last time, and copied the library file before trying to restore so less harm was done. |
A screenshot of Example (showing test.bib) I assume the log does not say anything? I mean, I assume, the backup file sized changed from large file to 0 kb. During that time, there should be logs from jabref.
|
Relevant files can be sent to web@jabref.org. Would be interesting to know exactly what text you entered and what you did before the crash happened. Since JabRef 5.8, backups are created automatically 20 seconds after changes to library files. Maybe the creation of a backup file coincided with you editing the library file, triggering the index out of bounds and crashing. |
I think I was writing a comment, switched to my chrome browser, then switched back to writing the comment, probably hitting the space bar and then it crashed. |
JabRef version
5.13 (latest release)
Operating system
Windows
Details on version and operating system
JabRef 100.0.0 Mac OS X 14.2.1 aarch64 Java 20.0.1 JavaFX 20+19
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Unfortunately, I don't really know what happened. I was writing a comment for an entry in my bibliography, when JabRef crashed and when I tried to reopen it said "restore recent libary" but the file (
library.bib
) is now empty (0kb) and the information seems lost. I have a backup from a week ago somewhere else so I'll probably recover, but I don't know what happened or how to reproduce it.Appendix
...
Log File
MacBook crash report
The text was updated successfully, but these errors were encountered: