Rebelle just lost an entire layer

I was painting, and suddenly, the layer I was painting on became blank. I was not doing anything out of the ordinary--just painting. So I tried undoing, and with each undo, the spot I was painting previous would come back, but only in little rectangles that cover the area of the brushtroke. It looks like this:

I tried to undo as much as I could, but since Rebelle only has limited steps of undos, I couldn't get far. I tried loading the autosave, but they all gave me the error message about there being an expected crash, and do I want to load an autosave version--which makes no sense since I was already trying to load an autosave version. And then when I clicked yet, it gave me this same glitched version instead of the previous autosave. I went two autosave back (my autosave is set to 10 minutes), and both gave me the same error. I then decided to save the current glitched version with a different name and close Rebelle, since I suspected having it open was causing past autosave to not load correctly. I was right. The most recent autosave was glitched too because it happened after the file had already glitched, but the version before that restored correctly.

I have 32 GB of RAM and it was only at about 50% usage at the time of the glitch. And my CPU usage was low. Nothing was out of the ordinary except for the glitch. 

In the past, I was fine with Rebelle sometimes crashing on me, because I could always load up the autosave and get right back to painting. But this kind of glitch is absolutely unacceptable, because it lost me work due to autosave unable to restore the previous version. Yes, I technically only lost about 10 minutes of work, but often with painting, those 10 minutes could contain expressive brushwork that can never be replicated again. 

If the devs wants my glitched Rebelle file to troubleshoot, I can upload it. 

BTW, I also have the timelapse video of the session, which shows the glitch happening. 

For those of you following this thread, the dev team also reached out to me via email, and if anything helpful comes out of our correspondence, I'll update this thread. For now, I'll just clarify that mis-pressing CTRL+X is not the issue, since I usually use the programmable buttons on my graphics tablet for undos. 

The issue has finally been fixed to Rebelle 7.1.3 version after struggling with the reproduction of this bug for years:

Modifying a layer (e.g. painting a short stroke or clear/cut layer) quickly after Undo / Redo and then invoking another Undo / Redo caused an unrecoverable data loss in the current layer (the bug caused loss of an entire layer, undoing caused the parts of the artwork to reappear in squares)