Intermittent crash with JPilot while syncing
Every ~ 10 runs I observe some kind of crash with latest JPilot.
When I run it with jpilot -d I often see caught signal SIGCHLD, but mostly without a notable crash.
Here a typical example in the 45th last line:
JPilot with signal SIGCHLD_2.log
There are different types of crashes, where I have no clue, what are the conditions for:
- Logging pane stops listing, and the complete GUI freezes.
- Sometimes I can close the app by the X button in the window title.
- But sometimes not, so I must kill it.
- Sometimes the sync has completed (sync button is again normal), but in few cases not.
- Sometimes after the cases above, on restart, all or partly custom settings and window size are lost, but sometimes not.
- Sometimes after the cases above, on restart, a complete initial sync is processed, which takes much longer than normal.
- Often changing the window focus from JPilot to another App makes a crash much more probable.
Fortunately I never observed a real data loss.
Maybe some ideas on that?
Here the last lines of a crash with GUI freeze again.
[..........]
calling plugin_post_sync for [KeyRing 1.1]
KeyRing: plugin_post_sync
calling plugin_post_sync for [Expense 1.1]
Expense: plugin_post_sync
calling plugin_post_sync for [Media 1.1]
Media: plugin_post_sync -> done.
freeing plugin list
Fertig.
unlock succeeded
sync child exiting
command=100 [Fertig.
]
command=105 [
]
address_gui_cleanup()
jp_pref_write_rc_file()
caught signal SIGCHLD
Getötet
Often I see jp_pref_write_rc_file() as the last action before the crash.
On the next start I saw:
- All preferences were lost
- The sync took unusually long time, because it seems, that all databases were copied newly instead only syncing changed records.
Honestly, from the information provided I do not know what the root cause is.
To narrow down the problematic location:
- Can you try to sync multiple times again with the Media plugin disabled?
- If that works for 10-20 times, then try the same for Expense, then for KeyRing, i.e., disable one plugin after the other.
For generating additional information, please monitor which files are modified, see inotify-tools: inotifywait.
I now can tell, that I tried several times without my Media plugin, but the crash still happens sometimes. It happens much more often since using Ubuntu 24.04 than with 22.02.
In furture I will use it without Expense, Keyring and SQLite, because I don't need theese data bases.
Am 18.03.25 um 20:45 schrieb Elmar Klausmeier:
Honestly, from the information provided I do not know what the root cause is.
To narrow down the problematic location:
- Can you try to sync /multiple times/ again with the Media plugin disabled?
- If that works for 10-20 times, then try the same for Expense, then for KeyRing, i.e., disable one plugin after the other.
For generating additional information, please monitor /which/ files are modified, see inotify-tools: inotifywait https://eklausmeier.goip.de/blog/2013/01-29-inotify-tools-inotifywait.
— Reply to this email directly, view it on GitHub https://github.com/juddmon/jpilot/issues/53#issuecomment-2734532997, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADQ7UBSJIPLUVBCCLNIE7KT2VBZWNAVCNFSM6AAAAABZIZANRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZUGUZTEOJZG4. You are receiving this because you authored the thread.Message ID: @.***>
eklausmeeklausme left a comment (juddmon/jpilot#53) https://github.com/juddmon/jpilot/issues/53#issuecomment-2734532997
Honestly, from the information provided I do not know what the root cause is.
To narrow down the problematic location:
- Can you try to sync /multiple times/ again with the Media plugin disabled?
- If that works for 10-20 times, then try the same for Expense, then for KeyRing, i.e., disable one plugin after the other.
For generating additional information, please monitor /which/ files are modified, see inotify-tools: inotifywait https://eklausmeier.goip.de/blog/2013/01-29-inotify-tools-inotifywait.
— Reply to this email directly, view it on GitHub https://github.com/juddmon/jpilot/issues/53#issuecomment-2734532997, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADQ7UBSJIPLUVBCCLNIE7KT2VBZWNAVCNFSM6AAAAABZIZANRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMZUGUZTEOJZG4. You are receiving this because you authored the thread.Message ID: @.***>