My 1st VST Live crash

Hi, I had my 1st crash. Admittedly the unit had been left on overnight, and the following morning there was a crash relating to VST Live.

Here it is, if its of any use?


Translated Report (Full Report Below)

Process: vstlive [31609]
Path: /Applications/VST Live.app/Contents/MacOS/vstlive
Identifier: com.steinberg.vstlive
Version: 1.0.40.596 (1.0.40.596)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2022-08-11 07:26:28.6179 +1000
OS Version: macOS 12.4 (21F79)
Report Version: 12
Anonymous UUID: 5E6F039E-F7DC-3ECC-F798-88F9935F2745

Sleep/Wake UUID: 020106DE-DE6B-429A-AC40-5F2F9C90632E

Time Awake Since Boot: 320000 seconds
Time Since Wake: 124507 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 0x00008e7e875ffb78 → 0x00000e7e875ffb78 (possible pointer authentication failure)
Exception Codes: 0x0000000000000001, 0x00008e7e875ffb78
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [31609]

VM Region Info: 0xe7e875ffb78 is not in any region. Bytes after previous region: 15455563545465 Bytes before following region: 50079668896904
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
commpage (reserved) 1000000000-7000000000 [384.0G] —/— SM=NUL …(unallocated)
—> GAP OF 0x3b9a9c400000 BYTES
JS JIT generated code 3c0a9c400000-3c0a9c401000 [ 4K] —/rwx SM=NUL

Kernel Triage:
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 vstlive 0x102feca7b 0x102cf9000 + 3095163
1 vstlive 0x102fef467 0x102cf9000 + 3105895
2 vstlive 0x1031a6ac1 0x102cf9000 + 4905665
3 vstlive 0x1031a818e 0x102cf9000 + 4911502
4 vstlive 0x102fff805 0x102cf9000 + 3172357
5 vstlive 0x102fffaf4 0x102cf9000 + 3173108
6 dyld 0x20709251e start + 462

Thread 1:: com.apple.rosetta.exceptionserver
0 runtime 0x7ff7ffe649c4 0x7ff7ffe60000 + 18884
1 runtime 0x7ff7ffe72460 0x7ff7ffe60000 + 74848
2 runtime 0x7ff7ffe73ed8 0x7ff7ffe60000 + 81624

Thread 2:: org.libusb.device-hotplug
0 ??? 0x7ff89da6e940 ???
1 libsystem_kernel.dylib 0x7ff80d4b897a mach_msg_trap + 10
2 libsystem_kernel.dylib 0x7ff80d4b8ce8 mach_msg + 56
3 CoreFoundation 0x7ff80d5bb540 __CFRunLoopServiceMachPort + 319
4 CoreFoundation 0x7ff80d5b9bd0 __CFRunLoopRun + 1276
5 CoreFoundation 0x7ff80d5b9014 CFRunLoopRunSpecific + 562
6 CoreFoundation 0x7ff80d640547 CFRunLoopRun + 40
7 vstlive 0x1040794fa 0x102cf9000 + 20448506
8 libsystem_pthread.dylib 0x7ff80d4f54e1 _pthread_start + 125
9 libsystem_pthread.dylib 0x7ff80d4f0f6b thread_start + 15

Thread 3:
0 ??? 0x7ff89da6e940 ???
1 libsystem_kernel.dylib 0x7ff80d4bf0aa poll + 10
2 vstlive 0x104075598 0x102cf9000 + 20432280
3 vstlive 0x10407501b 0x102cf9000 + 20430875
4 vstlive 0x104075ae1 0x102cf9000 + 20433633
5 vstlive 0x104068411 0x102cf9000 + 20378641
6 libsystem_pthread.dylib 0x7ff80d4f54e1 _pthread_start + 125
7 libsystem_pthread.dylib 0x7ff80d4f0f6b thread_start + 15

Thread 4:: com.apple.NSEventThread
0 ??? 0x7ff89da6e940 ???
1 libsystem_kernel.dylib 0x7ff80d4b897a mach_msg_trap + 10
2 libsystem_kernel.dylib 0x7ff80d4b8ce8 mach_msg + 56
3 CoreFoundation 0x7ff80d5bb540 __CFRunLoopServiceMachPort + 319
4 CoreFoundation 0x7ff80d5b9bd0 __CFRunLoopRun + 1276
5 CoreFoundation 0x7ff80d5b9014 CFRunLoopRunSpecific + 562
6 AppKit 0x7ff81009cc1e _NSEventThread + 132
7 libsystem_pthread.dylib 0x7ff80d4f54e1 _pthread_start + 125
8 libsystem_pthread.dylib 0x7ff80d4f0f6b thread_start + 15

Thread 5:: YYTransport
0 ??? 0x7ff89da6e940 ???
1 libsystem_kernel.dylib 0x7ff80d4bf0aa poll + 10
2 vstlive 0x104c6aece 0x102cf9000 + 32972494
3 vstlive 0x104c6c34c 0x102cf9000 + 32977740
4 vstlive 0x104c28907 0x102cf9000 + 32700679
5 vstlive 0x104ae829c 0x102cf9000 + 31388316
6 vstlive 0x104ae8e50 0x102cf9000 + 31391312
7 libsystem_pthread.dylib 0x7ff80d4f54e1 _pthread_start + 125
8 libsystem_pthread.dylib 0x7ff80d4f0f6b thread_start + 15

Thread 6:: AMCP Logging Spool
0 ??? 0x7ff89da6e940 ???
1 libsystem_kernel.dylib 0x7ff80d4b89b6 semaphore_wait_trap + 10
2 caulk 0x7ff8164592e6 caulk::mach::semaphore::wait_or_error() + 16
3 caulk 0x7ff816441148 caulk::concurrent::details::worker_thread::run() + 36
4 caulk 0x7ff816440e0c void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::)(), std::__1::tuplecaulk::concurrent::details::worker_thread* > >(void) + 41
5 libsystem_pthread.dylib 0x7ff80d4f54e1 _pthread_start + 125
6 libsystem_pthread.dylib 0x7ff80d4f0f6b thread_start + 15

Thread 7:: com.apple.audio.IOThread.client
0 ??? 0x7ff89da6e940 ???
1 libsystem_kernel.dylib 0x7ff80d4b897a mach_msg_trap + 10
2 libsystem_kernel.dylib 0x7ff80d4b8ce8 mach_msg + 56
3 CoreAudio 0x7ff80f076c87 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111
4 CoreAudio 0x7ff80ef01d6b HALC_ProxyIOContext::IOWorkLoop() + 3909
5 CoreAudio 0x7ff80ef0085d invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 63
6 CoreAudio 0x7ff80f0cc696 HALB_IOThread::Entry(void*) + 72
7 libsystem_pthread.dylib 0x7ff80d4f54e1 _pthread_start + 125
8 libsystem_pthread.dylib 0x7ff80d4f0f6b thread_start + 15

SNIP - Sorry restricted text amount.

Hi @Darug,

Thank you. Yes, every crash log is important and helpful. We have analysed it. VL crashed while you have closed it. Correct? Do you remember what was visible? MediaBay? Which category? Lower Zone? Any break out window (LAYERS, TRACKS, …) opened?

See you,
Michael.

I don’t recall exactly, but I haven’t really done too much yet with the software. There were probably 8 songs, and I only use 1 part. There were possibly 3 seperate layers. I usually shutdown Audio software, mainly due to the amount of times Mainstage crashes overnight, or loses the Audio Interface (when changing location).

… thank you. We’ve fixed it.

Michael.

1 Like

I just installed it yesterday and regret it already. very unstable, loosing contact with my keyboard (USB, roland FA), volume faders not interacting well with vsts, new layers keep silent. and this in only the first 30 minutes of using it. Have you tested this product before you brought it to market?

2 Likes

Of course it has been tested and used on stage.
New Layers may be silent if no sound (preset) has been loaded into the Instrument. Open Instrument Editor, apply a preset so you get sound, and then apply menu Layers/Save Default Layer to bring up that sound every time you create a new Layer.
For the other comments of yours, we need more details, for instance “volume faders not interacting well with vsts” don’t know what you mean? “loosing contact with my keyboard” - what precisely is the problem, what is your system, what Instrument used? Also make sure to use the latest version of VST Live (1.0.41 as of this writing).

of course it’s been tested but it is irritating when it is not working properly, fyi a preset is loaded and no sound, loosing contact with keyboard (roland fa7) means, doesnot respond anymore to keyboard after changing midi channels, turning knobs and all these kind of testing . I will try to figure out what causes the problem. it could be the settings of notebook (dell i7 intel), the software, the usb connection or the vsts .

forgot, yes version 1.0.41 greetings, Johan, midifreak for 35 years

BTW requested a refund for VST lIve. tired of all the bugs. no VST Live for me for the time being

Appears the system didn’t inform about this post, sorry to have missed it.

Which instrument, which preset? What do you do, what happens (not)?

Where did you change channel? Beeing a midi freak you are aware that Layers filter by input channel. Pls let us know exactly what you do and what doesn’t happen as you expect. Changing midi chnl. on my keyboard VST Live reacts exactly as expected, if it doesn’t for you, please help us and others to find out what we appear to miss?

Sorry to hear that. We are close to a new version with many improvements, so maybe you try that first. But most of all we miss your reports so to help us and most of all, help other users.