Hello Maxim,
Sorry for this late reply. I have version 4.2 now and while working on a 6GB 1280x720 H.264 file, it has unexpectedly quit twice. The app window disappears and the macOS problem report window to send debug info to Apple pops up. I suppose it could be due to the MacBook Air I'm using (13-inch, Early 2015) with only 8GB memory and 29GB of storage free is underpowered for the task. Here below is how the macOS problem report begins. I've saved the entire 1022 line report in case it's helpful. I'll try to use 4.2 on a newer MacBook Pro later.
Thanks,
Derek
Process: SolveigMM Video Splitter 4 [91286]
Path: /Applications/SolveigMM Video Splitter 4.app/Contents/MacOS/SolveigMM Video Splitter 4
Identifier: com.solveigmm.VideoSplitterHome3
Version: 4.2 (1912.28)
App Item ID: 1220817427
App External ID: 834154843
Code Type: X86-64 (Native)
Parent Process:
[1]
Responsible: SolveigMM Video Splitter 4 [91286]
User ID: 502
Date/Time: 2020-01-17 21:40:12.286 +0800
OS Version: Mac OS X 10.14.4 (18E226)
Report Version: 12
Anonymous UUID: D79059C9-776B-87A7-4866-60E6EC75358D
Sleep/Wake UUID: 2398A25D-55E9-4A31-98BA-28ADE7B83AE0
Time Awake Since Boot: 2600000 seconds
Time Since Wake: 1000000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000002000000001
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [91286]
VM Regions Near 0x2000000001:
MALLOC_LARGE 0000000122a87000-0000000122adc000 [ 340K] rw-/rwx SM=PRV
-->
JS JIT generated code 00005ec1ade00000-00005ec1ade01000 [ 4K] ---/rwx SM=NUL
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libglib-2.0.0.dylib 0x000000010e601ced g_slice_alloc + 909
1 libglib-2.0.0.dylib 0x000000010e5b579d g_array_sized_new + 45
2 libgstreamer-1.0.0.dylib 0x000000010e452e66 gst_structure_new_id_empty + 70