Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crashes while trying to do a diff of two snapshots. #1197

Closed
paulstewartis opened this issue Nov 23, 2021 · 8 comments
Closed

Crashes while trying to do a diff of two snapshots. #1197

paulstewartis opened this issue Nov 23, 2021 · 8 comments
Labels
Bug Heisenbug a problem that is not reproducible but random (non-deterministic) Medium

Comments

@paulstewartis
Copy link

I selected a snapshot. Then chose a snapshot from the day before and clicked diff. The UI froze a for a long time and then the application crashed. I repeated this several times with different snapshots.

Backup target is ssh. Snapshots are ~1.2 GB in size. It's been a while but, I have successfully diffed snapshots on this system in the past. Diff tool is Meld. OS is opensuse Leap 15.3 (fully updated).

[i noticed a growing folder in /tmp that eventually filled the space (tmpfs at 25% ram ~974mb). I increased ram (vm) to 6GB and increased /tmp to 50% (~3GB). I attempted the diff again and the application still crashed. The temp folder was only a little over 1GB. Plenty of free ram too.]

@paulstewartis
Copy link
Author

Maybe a dupe of [(https://github.com//issues/1083)]

@buhtz
Copy link
Member

buhtz commented Sep 25, 2022

Tag: Qt

@zbigniewfr
Copy link

I'm experiencing the same problem.

@buhtz
Copy link
Member

buhtz commented Oct 14, 2022

Dear @paulstewartis and @zbigniewfr ,

I have a guess what it could be but can you show us the debug output please?
Start BIT in a terminal window via backintime-qt --debug.

@zbigniewfr
Copy link

zbigniewfr commented Oct 14, 2022

@buhtzz log from debug:


Back In Time
Version: 1.3.2

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

DEBUG: [common/backintime.py:670 getConfig] config file: /home/user/.config/backintime/config
DEBUG: [common/backintime.py:671 getConfig] share path: /home/user/.local/share/backintime
DEBUG: [common/backintime.py:672 getConfig] profiles: 1=Main profile
DEBUG: [common/pluginmanager.py:90 PluginManager.load] Register plugin path /usr/share/backintime/plugins
DEBUG: [common/pluginmanager.py:106 PluginManager.load] Add plugin qt4plugin.py
DEBUG: [common/pluginmanager.py:106 PluginManager.load] Add plugin notifyplugin.py
DEBUG: [common/tools.py:829 keyringSupported] No appropriate keyring found. 'keyring.backends.chainer' can't be used with BackInTime
DEBUG: [common/mount.py:73 Mount.__init__] pw-cache is not running
DEBUG: [common/mount.py:81 Mount.__init__] Call command: /usr/bin/backintime pw-cache start
DEBUG: [common/tools.py:1237 readCrontab] Read 2 lines from users crontab
DEBUG: [common/config.py:1466 Config.removeOldCrontab] Clearing system Back In Time entries
DEBUG: [common/config.py:1500 Config.cronLine] Profile: Main profile | Automatic backup: Every 6 hours
DEBUG: [common/tools.py:1274 writeCrontab] Wrote 2 lines to users crontab
Killed

I clicked snapshots -> Diff. The application stopped responding.

@emtiu
Copy link
Member

emtiu commented Oct 14, 2022

There's a traceback in #1083, which might be the same problem here. I'm not closing it as a duplicate yet, because we haven't seen identical error messages so far.

@emtiu emtiu added the Bug label Oct 14, 2022
@buhtz buhtz added this to the 1.3.5 / 1.4.0 milestone Mar 19, 2023
@buhtz
Copy link
Member

buhtz commented Jun 29, 2023

I have seen this with 1.3.4-dev but wasn't able to reproduce it for sure. 😄
The trigger seems to be the diff dialog but the output provided and I've seen myself indicates something around writeCrontab().

@buhtz buhtz added the Medium label Jun 29, 2023
@emtiu emtiu added the Heisenbug a problem that is not reproducible but random (non-deterministic) label Aug 25, 2023
@buhtz
Copy link
Member

buhtz commented Sep 10, 2024

The reason for the error is still unknown. But the code around writeContrab() was refactored a lot.

I will close this issue because of that. Please feel free to reopen it if the problem happens with the latest version of BIT.

@buhtz buhtz closed this as completed Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Heisenbug a problem that is not reproducible but random (non-deterministic) Medium
Projects
None yet
Development

No branches or pull requests

4 participants