search

ransome1 / sleek

todo.txt manager for Linux, Windows and MacOS, free and open-source (FOSS)
https://github.com/ransome1/sleek/wiki
MIT License
1.33k stars 104 forks source link

Sleek freezes, then crashes, leaves behind 0-byte ToDo.txt file #484

Closed TriggerDingus closed 10 months ago

TriggerDingus commented 1 year ago

Is it an actual bug? Yes

Did you check if the bug has already been reported? Yes

Describe the bug This has occurred twice now for me, each time on a different machine and a few weeks between each incident. Luckily, I keep daily backups and can restore my ToDo.txt file when it occurs though it can be a challenge to recall what was added/completed during the day. I've been using Sleek for a year or so (don't recall exactly-could be more) this seems to be rare, but it is scary because you know when the Sleek screen freezes for more than a couple seconds it's going to crash and leave behind a 0-byte ToDo.txt file. I can't reproduce this issue at-will because it occurs simply while using the application and while doing nothing of note. I may be completing an item, adding an item, whatever - the app just freezes for an extended period (10 seconds or more, maybe) before crashing and leaving behind the empty ToDo.txt file. My file is about 4400 lines, 356kb in size. I don't know that this is big/small/average - Sleek doesn't seem to have any issues with it except for these 2 rare occurrences that I describe here.

To Reproduce See above

Do you see any error entries in sleeks developer tools? See attached screen shot. cap1

Expected behavior N/A

Screenshots Attached

Desktop (please complete the following information):

ransome1 commented 1 year ago

I don't have the slightest idea why this happens and I have never experienced it myself.

I'm currently rewriting the base of sleek. Many things will be done differently and I simply hope this will be solved once 2.0 is production ready.

TriggerDingus commented 1 year ago

I appreciate the response and transparency. I may be jinxing myself, but this hasn't happened in a few months so who knows if it was an update to my OS that fixed it, or something else. Or, perhaps it isn't fixed and it's waiting for me to post this message before it shows itself again.

ransome1 commented 10 months ago

@TriggerDingus 2.0.0 has been released on GitHub. This issue should be addressed in that release. If it still occurs, let's re-open here.