I’ve experienced repeated crashes of the new version 1.2.3 on Ubuntu 14.10. Since this isn’t a Canonical app, I suspect apport cannot report these crashes. Please instruct me on how to gather the required information to troubleshoot this issue.
Hi,
Please try running Insync through gdb to capture the backtrace when it crashes.
- open a terminal
- cd /usr/lib/insync
- gdb --args ./insync start --no-daemon
- in the gdb prompt, run “r”
- when Insync crashes, run “bt” in the gdb prompt
- send the output to support@insynchq.com
This is embarrassing. I’m trying to catch a crash, but I’m having no luck so far.
I did give it up for a day, the day before yesterday, and got another one (obviously, I’ve got nothing to show for it), which leads me to asking: is it possible that an element of the app isn’t initialized when I start it inside a gdb shell? Or somehow operates differently? Is there another method I can try?
Thanks.
PS
That last crash was before the update to 1.2.6, which is what I’m running now. I haven’t tried running it outside gdb since the update, but I can if that’s advisable.
I don’t think there should be anything different if running Insync through gdb or not. Can you reproduce the crash consistently if running Insync normally? Is there a pattern with the crashes?
Not that I’ve discerned, but I’ll focus my efforts in that direction next. Thanks again.
Unfortunately, this still happens. It appears to occur even when I’m away from my desktop, when nothing new is syncing, unrelated to anything I might be doing with it. This, I might add, is the first day I’m trying to run it outside gdc, and just a few hours in I got this crash message again.
I see. Have you tried disabling notifications to see if there’s a difference?
No, disabling notification doesn’t resolve the issue.
Is there an entry in /var/crash for Insync? If there is please try sending it to support@insynchq.com.
Indeed there is, and I’ve sent it to you. Thanks.