AudioPluginHost instant crash when add new plugin

Just updated to the latest develop commit b01d8c36194888ff61c30699583445f00ab68d86

And I found when I debug my AU plugin on MacOS, it prints this

AudioPluginHost[5071:211543] Task .<1> finished with error [-1002] Error Domain=NSURLErrorDomain Code=-1002 “unsupported URL” UserInfo={NSLocalizedDescription=unsupported URL, NSErrorFailingURLStringKey=, NSErrorFailingURLKey=, _NSURLErrorRelatedURLSessionTaskErrorKey=(

“LocalDataTask .<1>”

), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask .<1>, NSUnderlyingError=0x600000da47e0 {Error Domain=kCFErrorDomainCFNetwork Code=-1002 “(null)”}}

Error Domain=NSURLErrorDomain Code=-1002 “unsupported URL” UserInfo={NSLocalizedDescription=unsupported URL, NSErrorFailingURLStringKey=, NSErrorFailingURLKey=, _NSURLErrorRelatedURLSessionTaskErrorKey=(

“LocalDataTask .<1>”

), _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask .<1>, NSUnderlyingError=0x600000da47e0 {Error Domain=kCFErrorDomainCFNetwork Code=-1002 “(null)”}}

then when I try to add a new plugin, I got instant crash,

at

_LIBCPP_INLINE_VISIBILITY
pointer get() const _NOEXCEPT {
return _ptr.first();

saying
JUCE Message Thread (1): EXC_BAD_ACCESS (code=1, address=0x98)

Even without debug, running the AudioPluginHost in standalone, this still happens, everything works fine under Reaper and GarageBand, not sure what’s going on, any suggestions? @fr810

Thanks for reporting this, it appears to be caused by a bad access at juce_Component.cpp:126. A fix should arrive shortly.

2 Likes

Cool! Thanks for the reply~

The fix is out on develop.

1 Like

Appreciated! Lock and load~