Insync 1.4.5 High Sierra crashes when clicked


#1

Insync starts syncing correctly, but if I click on the icon in the toolbar, it crashes. I’m syncing three accounts. The Trace/BPT trap on the last line occurs with the click.

Thanks,
Jason

[warn] kq_init: detected broken kqueue; not using.: No such file or directory
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file ‘/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist’
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8
/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file ‘/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist’
INFO 2018-04-07 09:08:18,623 [ipclistener:install_daemon:112] Starting FS Events Daemon
INFO 2018-04-07 09:08:18,627 [ipclistener:install_daemon:117] Daemon versions: 1.8(plist) and 1.8(app)
INFO 2018-04-07 09:08:18,684 [ipclistener:install_daemon:112] Starting FS Events Daemon
INFO 2018-04-07 09:08:18,689 [controller:checkBundle:250] Starting bundle check
INFO 2018-04-07 09:08:18,689 [ipclistener:install_daemon:117] Daemon versions: 1.8(plist) and 1.8(app)
INFO 2018-04-07 09:08:18,691 [ipclistener:install_daemon:112] Starting FS Events Daemon
INFO 2018-04-07 09:08:18,693 [ipclistener:install_daemon:117] Daemon versions: 1.8(plist) and 1.8(app)
INFO 2018-04-07 09:08:18,749 [controller:starterMethods:241] Done start client
INFO 2018-04-07 09:08:18,808 [gdsyncer:sync_account:153] Syncing GDUser(id=u’111219778721183890368’, email=u’jasonh@elided.com’, name=u’Jason Hickey’).
INFO 2018-04-07 09:08:19,387 [gdsyncer:sync_account:153] Syncing GDUser(id=u’110118947565937376574’, email=u’store@elided.com’, name=u’A Store’).
INFO 2018-04-07 09:08:25,724 [client:__on_gd_account_added:881] GDUser(id=u’111219778721183890368’, email=u’jasonh@elided.com’, name=u’Jason Hickey’) (existing) is now being synced.
INFO 2018-04-07 09:08:25,838 [gdsyncer:sync_account:153] Syncing GDUser(id=u’115864444421529840910’, email=u’jason@elided.com’, name=u’Jason Hickey’).
INFO 2018-04-07 09:08:28,755 [client:__on_gd_account_added:881] GDUser(id=u’110118947565937376574’, email=u’store@elided.com’, name=u’A Store’) (existing) is now being synced.
INFO 2018-04-07 09:08:52,513 [client:__on_gd_account_added:881] GDUser(id=u’115864444421529840910’, email=u’jason@elided.com’, name=u’Jason Hickey’) (existing) is now being synced.
INFO 2018-04-07 09:09:36,863 [_updater:_run:113] No updater available.
Trace/BPT trap


#2

same here, and it happened after the today’s update of my MacOS Sierra system (10.13.4)


#3

any news on this. it worked fine until yesterday for me. same symptoms. macos update 10.13.4 on the 7th of april but only now the crash occurs.
i uninstalled insync and wanted to install again but now when connection with server is made via login and authenticate via website, insync crashes.
as insync is integrated in our company workflow, we need this thing up & running again. please advise


#5

Yep - I also have this issue. Doesn’t seem to be an easy work around so far?


#6

Same problem here with macOS High Sierra 10.13.4


#7

I have the same issue. I tried to look into the error log /private/var/log/insync.error.log. It was too long…so I deleted it and hoped there will be some new log out. However, there was none…


#8

Hi @Jason_Hickey @Gabriele_Grecchi @mr-becker @Oliver_Jobson @qjuanp @astroboylrx

I apologize for not replying sooner! Our engineer is currently investigating on this as we have also received similar cases via email.

In the meantime, may I confirm if you guys can downgrade to 1.3.24? Let us know if you’re still encountering a crashing issue.

Thank you!


#9

insync is now working fine again. first after (re)installation, it wouldn’t work.
after some restarts, it worked on thursday. it was not stable on thursday and sometimes clicking on the icon,would make it crash. eventually it started working as intended on friday and has ever since.
so if you want an update of the log files, just let me know.


#10

i just downgraded to the version you recommended and it works just fine
should we wait to upgrade?


#11

I’ve downgraded, but I still get crashes. Most recent stack trace:

Thread 1 Crashed:
0 com.apple.WebCore 0x9d2de6f6 WebCore::TimerBase::~TimerBase() + 134
1 com.apple.WebCore 0x9d308081 WebCore::StyleResolver::~StyleResolver() + 289
2 com.apple.WebCore 0x9e5774ae WebCore::Style::Scope::scheduleUpdate(WebCore::Style::Scope::UpdateType) + 174
3 com.apple.WebCore 0x9e5778b1 WebCore::Style::Scope::didChangeStyleSheetEnvironment() + 161
4 com.apple.WebCore 0x9d2c0e25 WebCore::Page::setDeviceScaleFactor(float) + 85
5 com.apple.WebKitLegacy 0x9e88d88b -[WebView _windowDidChangeBackingProperties:] + 155
6 com.apple.Foundation 0x95184a6f __57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_2 + 32
7 com.apple.CoreFoundation 0x9378f812 CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 18
8 com.apple.CoreFoundation 0x9378f6c1 _CFXRegistrationPost + 481
9 com.apple.CoreFoundation 0x9378f3b9 ___CFXNotificationPost_block_invoke + 201
10 com.apple.CoreFoundation 0x937500a3 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1555
11 com.apple.CoreFoundation 0x9374f037 _CFXNotificationPost + 631
12 com.apple.Foundation 0x951480e9 -[NSNotificationCenter postNotificationName:object:userInfo:] + 71
13 com.apple.AppKit 0x91c175c0 -[NSWindow _postWindowDidChangeBackingPropertiesAndDisplayWindowForPreviousBackingScaleFactor:previousColorSpace:] + 204
14 com.apple.AppKit 0x914f6a89 __67-[NSWindow _updateSettingsSendingScreenChangeNotificationIfNeeded:]_block_invoke + 259
15 com.apple.AppKit 0x91492330 NSPerformVisuallyAtomicChange + 212
16 com.apple.AppKit 0x9141e512 -[NSWindow _updateSettingsSendingScreenChangeNotificationIfNeeded:] + 210
17 com.apple.AppKit 0x9141de29 -[NSWindow _setFrame:updateBorderViewSize:] + 1143
18 com.apple.AppKit 0x91433d45 -[NSWindow _oldPlaceWindow:] + 585
19 com.apple.AppKit 0x91433389 -[NSWindow _setFrameCommon:display:stashSize:] + 2869
20 com.apple.AppKit 0x9143284c -[NSWindow _setFrame:display:allowImplicitAnimation:stashSize:] + 217
21 com.apple.AppKit 0x914f67b2 -[NSWindow setFrameOrigin:] + 445
22 _objc.so 0x0974d75d ffi_call_SYSV + 29
23 _objc.so 0x0974da79 ffi_call + 89
24 _objc.so 0x09766c89 PyObjCFFI_Caller + 2793
25 _objc.so 0x0978b17a PyObjCSelector_GetClass + 1162
26 org.python.python 0x063092bd PyObject_Call + 101
27 org.python.python 0x06390852 PyEval_EvalFrameEx + 18514
28 org.python.python 0x063923ab PyEval_EvalCodeEx + 1780
29 org.python.python 0x0632d76e PyClassMethod_New + 1751
30 org.python.python 0x063092bd PyObject_Call + 101
31 _objc.so 0x0978d79f PyObjCSelector_FromFunction + 2895
32 org.python.python 0x063092bd PyObject_Call + 101
33 org.python.python 0x06390852 PyEval_EvalFrameEx + 18514
34 org.python.python 0x063923ab PyEval_EvalCodeEx + 1780
35 org.python.python 0x0632d76e PyClassMethod_New + 1751
36 org.python.python 0x063092bd PyObject_Call + 101
37 _objc.so 0x0978d79f PyObjCSelector_FromFunction + 2895
38 org.python.python 0x063092bd PyObject_Call + 101
39 org.python.python 0x06390852 PyEval_EvalFrameEx + 18514
40 org.python.python 0x063905f4 PyEval_EvalFrameEx + 17908
41 org.python.python 0x063905f4 PyEval_EvalFrameEx + 17908
42 org.python.python 0x063923ab PyEval_EvalCodeEx + 1780
43 org.python.python 0x0632d706 PyClassMethod_New + 1647
44 org.python.python 0x063092bd PyObject_Call + 101
45 org.python.python 0x06390dfe PyEval_EvalFrameEx + 19966
46 org.python.python 0x063923ab PyEval_EvalCodeEx + 1780
47 org.python.python 0x0632d706 PyClassMethod_New + 1647
48 org.python.python 0x063092bd PyObject_Call + 101
49 org.python.python 0x063163c2 PyClass_IsSubclass + 4374
50 org.python.python 0x063092bd PyObject_Call + 101
51 org.python.python 0x0638b278 PyEval_CallObjectWithKeywords + 171
52 greenlet.so 0x067187c0 initgreenlet + 7408
53 greenlet.so 0x067177b6 initgreenlet + 3302
54 greenlet.so 0x06717c4d initgreenlet + 4477
55 org.python.python 0x063092bd PyObject_Call + 101
56 core.so 0x066b8aea 0x66a0000 + 101098
57 libevent-2.0.5.dylib 0x066e21c1 event_base_loop + 3450
58 libevent-2.0.5.dylib 0x066e24ce event_dispatch + 35
59 core.so 0x066a8f81 0x66a0000 + 36737
60 org.python.python 0x063901e4 PyEval_EvalFrameEx + 16868
61 org.python.python 0x063923ab PyEval_EvalCodeEx + 1780
62 org.python.python 0x0632d76e PyClassMethod_New + 1751
63 org.python.python 0x063092bd PyObject_Call + 101
64 org.python.python 0x063163c2 PyClass_IsSubclass + 4374
65 org.python.python 0x063092bd PyObject_Call + 101
66 org.python.python 0x0638b278 PyEval_CallObjectWithKeywords + 171
67 greenlet.so 0x067187c0 initgreenlet + 7408
68 greenlet.so 0x067177b6 initgreenlet + 3302
69 ??? 0x063fb5f0 _Py_ZeroStruct + 12


#12

@Gabriele_Grecchi @mr-becker You can stay on 1.3.24 first while we work on a fix for v1.4. :slight_smile: Glad to know your current version works fine.

@Jason_Hickey Kindly send your latest log files to support@insynchq.com w/ the link to this post. Sorry for the trouble! :frowning:


#13

If I restart it works for a bit but then starts crashing again. Getting very annoying now…


#14

I’ve just seen there’s a minor update out from 1.4.5.37063 to 1.4.5.37069 so I will install that and see if it improves things.


#15

Nope… lived with it for a couple of days through multiple restarts. Anyone have any idea how I can roll back to the old one? I didn’t have access to team drives, but the bloody thing worked and no one seems to be helping here…


#16

Hi @Oliver_Jobson

I deeply apologize for the late reply! You may revert back to 1.3.24. Tagging our engineer @marte for further assistance.


#17

ok - that’s good to know. Are there clear instructions available for reverting back? I worry about loosing data when I mess with it too much.


#18

I’m having issues too, this is what OSX is telling me, basically there is no more compatibility with 32bits apps

After that, if I click the icon in the trybar Insync dissapears

Looking forward to a quick resolution.


#19

Hi Oliver,

You just need to right-click Insync on your tray and click “Quit”. After which, you can run 1.3.24.


#20

Hi,

Sorry for the inconvenience. :frowning: Please revert back to 1.3.24 while we work on the fixes.


#21

There are issues also with 1.3.24: same problem (crashing on click)
How can I send you the error log?