Exported Plugin occasionally crashes when switching sample maps



  • Hey guys,

    Some of my test users are occasionally experiencing plugin crashes when switching between sample maps in the exported plugin. The crashed thread is always "Pool". I've uploaded the relevant parts of the crash report below. Has anyone run into this issue before?

    Process:               Logic Pro X [5351]
    Path:                  /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
    Identifier:            com.apple.logic10
    Version:               10.4.6 (5088)
    Build Info:            MALogic-5088000000000000~2
    App Item ID:           634148309
    App External ID:       831740754
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Logic Pro X [5351]
    User ID:               501
    
    PlugIn Path:             /Library/Audio/Plug-Ins/Components/CUBE.component/Contents/MacOS/CUBE
    PlugIn Identifier:       com.myCompany.product
    PlugIn Version:          0.6.2 (0.6.2)
    
    Date/Time:             2020-11-12 15:07:45.301 -0500
    OS Version:            Mac OS X 10.14.6 (18G87)
    Report Version:        12
    Anonymous UUID:        B16D2CF5-9E88-2423-88D6-53A076A93C26
    
    
    Time Awake Since Boot: 23000 seconds
    
    System Integrity Protection: enabled
    
    Crashed Thread:        39  Pool
    
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       EXC_I386_GPFLT
    Exception Note:        EXC_CORPSE_NOTIFY
    
    Termination Signal:    Segmentation fault: 11
    Termination Reason:    Namespace SIGNAL, Code 0xb
    Terminating Process:   exc handler [5351]
    
    Application Specific Information:
    MALondonIII | e84d8ecce95d250e32c0f73d4c79d2b685e8718a80997af9a2b0f6c679216e01 | 28ef55f40e5dbf5cba062f4ca06868a3dc8a114d | 2019-07-04_15:24:24
    
    Thread 39 Crashed:: Pool
    0   com.myCompany.product         	0x00000001387eda70 0x138666000 + 1604208
    1   com.myCompany.product         	0x00000001392d9e99 0x138666000 + 13057689
    2   com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    3   com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    4   com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    5   com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    6   com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    7   com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    8   com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    9   com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    10  com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    11  com.myCompany.product         	0x00000001392da23b 0x138666000 + 13058619
    12  com.myCompany.product         	0x000000013935b6a6 0x138666000 + 13588134
    13  com.myCompany.product         	0x000000013935a8a5 0x138666000 + 13584549
    14  com.myCompany.product         	0x000000013935abad 0x138666000 + 13585325
    15  com.myCompany.product         	0x00000001391e0616 0x138666000 + 12035606
    16  com.myCompany.product         	0x00000001391bd99a 0x138666000 + 11893146
    17  libsystem_pthread.dylib       	0x00007fff790222eb _pthread_body + 126
    18  libsystem_pthread.dylib       	0x00007fff79025249 _pthread_start + 66
    19  libsystem_pthread.dylib       	0x00007fff7902140d thread_start + 13
    


  • Are all users who experience the issue using Logic? With the AU version of your plugin? Does the crash happen when they switch sample maps during playback or when the transport is stopped??



  • @d-healey Good q's – I've experienced a similar crash in the standalone, although less frequently. The others have all been in Logic using AU. Let me check with my testers if they were switching during playback, but I doubt it as we're still in preset development phase.



  • So it has never happened during playback. The transport is always stopped.



  • Need more info.

    So far it's only happening in Logic (and occasional, possibly related crash is happening in Standalone).
    Does it also happen with the VST version?
    Does it happen in any other DAW?
    Can it be recreated on demand or is it intermittent?
    What method is being used to switch sample maps? Does it also change preset at the same time?



  • So far it's only happening in Logic (and occasional, possibly related crash is happening in Standalone).
    Does it also happen with the VST version?
    Does it happen in any other DAW?

    I'm having trouble replicating the crashes in other DAWs. I've seen this error on some other forums be directly related to Logic:

    MALondonIII | e84d8ecce95d250e32c0f73d4c79d2b685e8718a80997af9a2b0f6c679216e01 | 28ef55f40e5dbf5cba062f4ca06868a3dc8a114d | 2019-07-04_15:24:24
    
    

    Can it be recreated on demand or is it intermittent?

    It's intermittent.

    What method is being used to switch sample maps? Does it also change preset at the same time?

    Presets are not being changed during the crash. I'm just using this function to swap sample maps:

    sampler.loadSampleMap(sampleMapId);
    

    I do set the pitch tracking value before calling this (this is necessary in case the user has turned it off for the previous sound), but not sure if that would make a difference:

    sampler.setAttribute(9, 1);
    


  • I think more expertise is required @Christoph-Hart


Log in to reply
 

12
Online

881
Users

3.2k
Topics

26.6k
Posts