-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug in Logic? #7221
Comments
which version of surge? I have a suspicion there may be a permissions problem which 1.23 can tickle which we have fixed in the nightly. If you start the application "Console" and go to "Crash Logs" is there anything there related to audio you could share? Has surge ever worked for you? |
Thanks for the quick response I am not well versed in code but this is from, what I believe to be, the crash log **Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 I am not sure if I have version 1.23 |
Yeah that’s the log if you can attach it all that would help greatly latest stable is here https://surge-synthesizer.github.io/ and development nightly which may solve the problem if thst doesn’t work is here |
Translated Report (Full Report Below)Process: Surge XT [59537] Date/Time: 2023-09-24 21:28:34.2513 -0400 Sleep/Wake UUID: 651101C3-092A-48AC-BE25-6AD6FBDE2A6A Time Awake Since Boot: 1100000 seconds System Integrity Protection: enabled Crashed Thread: 0 JUCE Message Thread Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0x17 is not in any region. Bytes before following region: 105553518919657 Thread 0 Crashed:: JUCE Message Thread Dispatch queue: com.apple.main-thread Thread 1: Thread 2: Thread 3: Thread 4: Thread 5:: caulk.messenger.shared:17 Thread 6:: MacBook Pro Speakers Thread 7:: com.apple.audio.IOThread.client Thread 8:: com.apple.audio.IOThread.client Thread 0 crashed with ARM Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary:
REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"Surge XT","timestamp":"2023-09-24 21:28:35.00 -0400","app_version":"1.2.3","slice_uuid":"e372b3fd-8854-3bae-9072-5dfa1e010094","build_version":"1.2.3","platform":1,"bundleID":"org.surge-synth-team.surge-xt","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 13.5 (22G74)","roots_installed":0,"name":"Surge XT","incident_id":"BB301375-7A2F-47DF-BCEC-7BE053AD3842"}
], Model: MacBookPro18,1, BootROM 8422.141.2, proc 10:8:2 processors, 16 GB, SMC |
Super useful thank you ii think what is happening is we respond poorly to not being able to open a file, probably documents directory. Surge should ask for that permission but if you say no we probably explode does your Logic Pro have access to the documents folder in security setting pane? if that doesn’t make sense I can give some more fulsome debugging info tomorrow, and of course if that fixes it we should fix surge and this stack trace would let me do so. I can also try some nightly tweaks to be more resilient if needs be thank you |
Potentially addresses surge-synthesizer#7221
I just merged the last in a series of defensive changes which should fix this I think. Can you sometime after about 2 hours from now try a nightky build and let us know if it scans for you in logic? thanks so much |
@dsnelson1990 Care to share some feedback with us if the latest nightly works fine for you now? Thanks! |
I'm gonna leave this open but bounce it out of the milestone. |
Hi there, Sorry to resurrect this again. I uninstalled and re-installed my favorite plugin and I am still receiving the same issue. . . |
you installed 1.3.1? Did you get a crash log for the version? |
Translated Report (Full Report Below)Process: Logic Pro X [41641] Date/Time: 2024-02-13 12:04:13.6707 -0500 Sleep/Wake UUID: 224215AC-2E6D-4D7B-BE8C-790A09BDD199 Time Awake Since Boot: 280000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0 is not in any region. Bytes before following region: 4302204928 Kernel Triage: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1:: com.apple.rosetta.exceptionserver Thread 2:: caulk.messenger.shared:17 Thread 3: Thread 4: Thread 5: Thread 6:: com.apple.NSEventThread Thread 7:: MIDIClientNotificationThread Thread 8:: SeqTimer 2 Thread 9: Thread 10:: CVDisplayLink Thread 11:: com.apple.audio.IOThread.client Thread 12:: com.apple.audio.IOThread.client Thread 13:: ProcessThread1 Thread 14:: ProcessThread2 Thread 15:: ProcessThread3 Thread 16:: ProcessThread4 Thread 17:: ProcessThread5 Thread 18:: ProcessThread6 Thread 19:: ProcessThread7 Thread 20:: FileIOThread 4 Thread 21:: FileIOThread 3 Thread 22:: FileIOThread 2 Thread 23:: FileIOThread 1 Thread 24:: com.apple.CFSocket.private Thread 25: Thread 26:: MetronomeUItriggerThread Thread 27:: CVDisplayLink Thread 28: Thread 29:: CVDisplayLink Thread 0 crashed with X86 Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary:
REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"Logic Pro X","timestamp":"2024-02-13 12:04:16.00 -0500","app_version":"10.8.1","slice_uuid":"c2f5387e-ce7e-3a3b-bf00-43a141e9f741","adam_id":"634148309","build_version":"5906","platform":1,"bundleID":"com.apple.logic10","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 13.5 (22G74)","roots_installed":0,"name":"Logic Pro X","incident_id":"A6888B51-5B3B-4D10-B7A8-53E16B4623EC"}
], ] |
Hmm. So you are running under rosetta but I guess you know that. It also shouldn't crash. The one thing I can think of is logic doesn't have access to your documents folder and that is causing surge to crash for you. What do you see in this settings screen? I can try and turn it off and see if logic surge crashes for me too maybe? |
hmm well that's not it then! I'll try and make a debugging build for you this week. How strange. |
Do me one favor also There's a folder Leave the folder there but move all the contents from the folder out. Does it start then? Or is that folder empty? Thanks so much. |
Oh my!!! It worked! Thank you so much!!!! Surge XT is by far my favorite synth and I've been lost without it. |
Ahh great. So if you don't mind: Can you send me the contents which you moved away? I would love to know what file is crashing it. Even if you have corrupted awfulness we shouldn't explode obviously! You can just zip them up and attach them here. |
@dsnelson1990 Do you still have the files you've moved away? We'd like to investigate them! |
I guess I'm closing this issue now due to inactivity and no response... |
Bug Description:
Error while booting up SurgeXT in Logic Pro X
"An Audio Unit plug-in reported a problem which might cause the system to become unstable. Please quit and restart Logic Pro."
Surge XT Version
This information is found on the About screen, which you get to from the bottom right menu.
VST plugin
Reproduction Steps:
Steps to reproduce the behavior:
Expected Behavior:
Expected the plugin to boot up but was unable to load the plugin period.
Screenshots:
Apple M1 Pro
Ventura 13.5 (22G74)
The text was updated successfully, but these errors were encountered: