-
Notifications
You must be signed in to change notification settings - Fork 285
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
Crashes type EXC_BAD_ACCESS KERN_INVALID_ADDRESS, SuperpoweredIOSAudioIO incorrect data writing #787
Comments
Could you please try with the latest update to the SuperpoweredIOSAudioIO class? |
Hello! I'll check it and get back to you with the results. We will have more results after we release the app. |
Some memory handling is wrong in your Superpowered.mm file, and therefore the Superpowered features you're using are crashing. Please check your buffer sizes. |
Superpowered version: 2.6.6
Describe the bug
My app uses Superpowered SDK to create different effects: AutomaticVocalPitchCorrection, ThreeBandEQ, TimeStretching, Bitcrusher, etc.
Now I have a lot of reports from Firebase Crashlytics
A lot of problems arise in the variable "samplerate" from class SuperpoweredIOSAudioIO that comes with the SDK.
Xcode shows a lot of Warnings in this class, for example
"This code path does interprocess communication underneath which can cause non-deterministic delays. Investigate ways to do this work off the main thread
There are reports of this code path causing UI hangs. See Xcode Organizer for details . Look for the report that shows calls to -[AVAudioSession currentRoute] underneath"
I think that SuperpoweredIOSAudioIO writes incorrect data to the samplerate variable, which is then used by other SuperpoweredSDK objects.
Can you fix this?
Steps to Reproduce
Due to the nature of the bug, the reproduction paths vary, and the crash does not happen predictably, making it challenging to outline specific steps to trigger the issue.
Device information
Please list which devices have this bug.
The text was updated successfully, but these errors were encountered: