Insync-portable aborts, loses linked account info

I’m using insync-portable v1.2.17 on Amazon Linux (sort of centos 6). It routinely crashes after some time. I’ll provide a backtrace from the core below. This isn’t a huge problem, because I can restart from cron. The more bothersome issue is that when this happens, insync loses linked account information and I have to delete the synced copy, link my account again, and start over. This makes insync essentially unusable for me since it means I almost never have a full sync, and I never know whether insync is even currently running without checking ps.

Backtrace:

    Program terminated with signal 6, Aborted.
#0  0x00007fa7dcb9500b in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
37        return INLINE_SYSCALL (tgkill, 3, pid, THREAD_GETMEM (THREAD_SELF, tid),
(gdb) bt
#0  0x00007fa7dcb9500b in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
#1  <signal handler called>
#2  0x00007fa7dc0f15c9 in __GI_raise (sig=sig@entry=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#3  0x00007fa7dc0f2cd8 in __GI_abort () at abort.c:90
#4  0x00007fa7dc0ea536 in __assert_fail_base (
    fmt=0x7fa7dc23a0e8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
    assertion=assertion@entry=0x3652213fab "activeq != ((void *)0)", 
    file=file@entry=0x3652213f0e "event.c", line=line@entry=371, 
    function=function@entry=0x3652214150 "event_process_active") at assert.c:92
#5  0x00007fa7dc0ea5e2 in __GI___assert_fail (assertion=0x3652213fab "activeq != ((void *)0)", 
    file=0x3652213f0e "event.c", line=371, function=0x3652214150 "event_process_active")
    at assert.c:101
#6  0x0000003652206816 in event_base_loop ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libevent-1.4.so.2
#7  0x00007fa7d29e5fd5 in ?? () from /usr/lib/insync-portable-1.2.17.35187/client/gevent.core.so
#8  0x000000304aae300e in PyEval_EvalFrameEx ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libpython2.7.so.1.0
#9  0x000000304aae4c6e in PyEval_EvalCodeEx ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libpython2.7.so.1.0
#10 0x000000304aa6f1f1 in ?? ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libpython2.7.so.1.0
#11 0x000000304aa46993 in PyObject_Call ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libpython2.7.so.1.0
#12 0x000000304aa59a1f in ?? ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libpython2.7.so.1.0
#13 0x000000304aa46993 in PyObject_Call ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libpython2.7.so.1.0
#14 0x000000304aadcd23 in PyEval_CallObjectWithKeywords ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libpython2.7.so.1.0
#15 0x00007fa7d23b18b9 in ?? ()
   from /usr/lib/insync-portable-1.2.17.35187/client/greenlet-0.4.6-py2.7-linux-x86_64.egg/greenlet.so
#16 0x00007fa7d23b1266 in ?? ()
   from /usr/lib/insync-portable-1.2.17.35187/client/greenlet-0.4.6-py2.7-linux-x86_64.egg/greenlet.so
#17 0x000000304ad8c850 in ?? ()
   from /usr/lib/insync-portable-1.2.17.35187/client/libpython2.7.so.1.0
#18 0x00007fa7cc045364 in ?? ()
#19 0x0000000000000000 in ?? ()

@dgc Please send your logs to support@insynchq.com as well. They are located at ~/.config/Insync.