Re: MusicSequenceFileLoad Crash on iOS10 (AudioToolbox/MusicPlayer)
Re: MusicSequenceFileLoad Crash on iOS10 (AudioToolbox/MusicPlayer)
- Subject: Re: MusicSequenceFileLoad Crash on iOS10 (AudioToolbox/MusicPlayer)
- From: Douglas Scott <email@hidden>
- Date: Tue, 13 Sep 2016 10:30:16 -0700
Can you zip up the MIDI file and attach it to a reply here?
In addition, if you would please file a radar (and attach the MIDI file there as well) and include the ID of that radar in your reply here, it would really help move this issue along.
Thanks!!
-DS
> On Sep 11, 2016, at 7:25 AM, down to this <email@hidden> wrote:
>
> I've encountered a crash when invoking the AudioToolbox / MusicPlayer API method "MusicSequenceFileLoad()" to load the contents of a MIDI file (from the given URL) into a music sequence on an iOS10 device and would greatly appreciate some assistance from the community.
>
> Observations I've been able to make thus far:
>
> * The first time the VC is displayed which uses this MIDI file all processing runs without any issues. It's only the second time that the VC is loaded where the app crashes. (Which makes me believe that this may be related to memory management.) The issue can be recreated consistently.
>
> * This code has been working without issue in production on iOS7, 8, and 9 for 2+ years and also runs without issue on the iOS 10 Simulator but crashes silently on a iOS 10 device (iPad Pro). Device is running iOS 10.0.1.
>
> * No crash report is created on the device when this issue is encountered. No exception information or call stack is available when debugging within Xcode.
>
> * Checking the OSStatus result code from calling this function simply returns a value of -1 and does not indicate the reason for the failure.
>
> * Profiling for memory management issues (allocations, leaks, zombies), has not shown any information related to the crash.
>
> * Turning on the Zombie Objects option did not reveal any Zombie Objects.
>
> * Analyzing the application did not reveal any areas where memory was not being released.
>
> I'm at a bit of a loss given the lack of information when the crash occurs. If anyone has any suggestions on other ways in which I could debug this issue it would be greatly appreciated. I feel like it could be related to memory management however from what I can see I am handling memory appropriately (using ARC for the application and releasing C-API objects as needed) and profiling has not revealed any issues that I can see.
>
> Thanks in advance for your assistance!
>
> Best,
>
> Derek
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden