Thanks for responding Jay-Bob.
1. Yes, I have been using v.7.12.3.60 -1.0.5 (30). It was this version that was repeatedly crashing, and when I found a reference to v.7.12.4 I tried to update unsuccessfully.
2. The crashes have seemed to happen randomly, and most often when Safari is running in the background. I have now tried opening the identical set of 9 tabs which I usually have running in Safari, this time in Firefox with its own Web Clipper extension. So far, after 24 hours, Firefox has not crashed. (If it does soon I will get back to you.)
The Safari crashes happen, by the way, whether or not the Evernote app itself is open. The crashes have also occurred whether or not I have other Safari extensions enabled. I've tried testing a lot of variables for some months now, to attempt to pin it down before finally reporting the problem to you.
Below are slices of the crash report which seem most relevant:
Process: Safari [10159]
Path: /Applications/Safari.app/Contents/MacOS/Safari
Identifier: Safari
Version: 13.1 (13609.1.20.111.8)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Safari [10159]
User ID: 501
Date/Time: 2020-05-11 16:06:28.908 +0300
OS Version: Mac OS X 10.13.6 (17G12034)
Report Version: 12
Anonymous UUID: 08DF0677-C54C-6427-9C13-2536FF74B0F9
Time Awake Since Boot: 460000 seconds
System Integrity Protection: enabled
Crashed Thread: 22 Dispatch queue: com.apple.NSXPCConnection.user.com.evernote.web.clipper.extension.apple-extension-service
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007521de7bbec8
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]
VM Regions Near 0x7521de7bbec8:
Stack 000070000919f000-0000700009221000 [ 520K] rw-/rwx SM=COW thread 25
-->
MALLOC_TINY 00007fc080400000-00007fc080500000 [ 1024K] rw-/rwx SM=PRV
and:
Thread 22 Crashed:: Dispatch queue: com.apple.NSXPCConnection.user.com.evernote.web.clipper.extension.apple-extension-service
0 libobjc.A.dylib 0x00007fff548cb174 objc_release + 36
1 libxpc.dylib 0x00007fff5584737f _xpc_connection_dispose + 57
2 libxpc.dylib 0x00007fff55840be9 _xpc_dispose + 51
3 libxpc.dylib 0x00007fff55847309 -[OS_xpc_connection _xref_dispose] + 47
4 com.apple.Foundation 0x00007fff2f672122 -[NSXPCConnection dealloc] + 327
5 libsystem_blocks.dylib 0x00007fff5553f99d _Block_release + 111
6 libdispatch.dylib 0x00007fff554b7db8 _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff554cc217 _dispatch_queue_serial_drain + 635
8 libdispatch.dylib 0x00007fff554bf166 _dispatch_queue_invoke + 373
9 libdispatch.dylib 0x00007fff554ccf0d _dispatch_root_queue_drain_deferred_wlh + 332
10 libdispatch.dylib 0x00007fff554d0d21 _dispatch_workloop_worker_thread + 880
11 libsystem_pthread.dylib 0x00007fff55808fd2 _pthread_wqthread + 980
12 libsystem_pthread.dylib 0x00007fff55808be9 start_wqthread + 13
Here's hoping you can identify the problem – and remedy it!
All the best to all the team. And STAY SAFE!