I’ve been using Elan 6.0 on macOS 10.14 (Mojave) with no problem. Today I installed 6.1 and noticed that the name displays with the .app extension. Then, on selecting an exiting .eaf file, it didn’t call Elan to open; though from inside Elan 6.1 the file opened OK. Later I was trying to open another .eaf (I think, I’m not sure I recall) and Elan crashed (something I haven’t experienced in a long time). I’ve reverted to 6.0 for now. Just sharing this in case it is part of a pattern.
Thanks for reporting. Hopefully it is not part of a pattern, it’s too early to tell now.
In case you can easily find the fragment in the System’s log relevant to the crash, you’re welcome to post it here (just the few lines identifying the thread or library that crashed and only if it is not a big effort).
-Han
Thanks Han.
Are these the relevant lines (from system.log):
Mar 23 22:15:14 MacBook-Pro-3 SpiceRack[1032]: spiceInfo for nl.mpi.elan == (null)
Mar 23 22:15:35 MacBook-Pro-3 ELAN[8773]: objc[8773]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff8d0823f0) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x1668fff50). One of the two will be used. Which one is undefined.
Mar 23 22:15:36 MacBook-Pro-3 ELAN[8773]: assertion failed: 18G8022: libxpc.dylib + 90649 [522FA3AF-D3B1-3283-8EF4-8B17CB237B65]: 0x89
When the crash notification came up, I think I clicked on Report which is supposed to send to the developer, which you would get to see, right?
David
Hi David,
The Reports are sent to Apple, I don’t think they are distributed from there (we never received any of them at least).
Some comments on your log messages: I don’t SpiceRack, so I have no idea if that message is related to the crash.There seems to be some ambiguity in the Finder (a class implemented twice), but again no idea if that can be fatal. The libxpc assertion seems to be quite ‘normal’ and harmless.
So, no idea what actually causes the crash, nor why it would occur in 6.1 and not in 6.0.
Thanks for the effort anyway!
-Han
Hi David and Han,
Just to add. Me and my student also downloaded 6.1 one today - we were very excited about the new audio waveform from the video! We are both Mac users and have had exactly the same problem. However, we haven’t had any errors coming up - we just have to force quit the software because it gets stuck.
We’ve gone back to 6.0 for now.
Hi, thanks for adding this.
If you have to force quit ELAN, there might actually be useful information in the ELAN log. The log file(s) is/are in ELAN’s data folder. If there are more than 1, the last modified time can be an indication which one to look into.
You may also send it to me (han.sloetjes AT mpi.nl) for inspection. I tried to reproduce the problem but so far failed (macOS 10.15.7).