仪器和泄漏

Question

I am testing my app and I keep getting these leaks but none of them are in my code..I think, has anyone else had these issues?

__NSCFDictionary        0x5f8cfe0   48  AudioToolbox    SimAggregateDevice::SimAggregateDevice(__CFString const*, __CFString const*, long&)

Malloc 32 Bytes     0x5f83a00   32  AudioToolbox    SimAggregateDevice::SimAggregateDevice(__CFString const*, __CFString const*, long&)

Malloc 48 Bytes     0x5f839d0   48  AudioToolbox    SimAggregateDevice::SimAggregateDevice(__CFString const*, __CFString const*, long&)

Malloc 32 Bytes     0x5f839b0   32  AudioToolbox    CreateDictionaryForDevice(unsigned long)

Malloc 32 Bytes     0x5f83990   32  AudioToolbox    CreateDictionaryForDevice(unsigned long)
__NSCFDictionary        0x5f83960   48  AudioToolbox    CreateDictionaryForDevice(unsigned long)

Malloc 32 Bytes     0x5f83940   32  AudioToolbox    SimAggregateDevice::SimAggregateDevice(__CFString const*, __CFString const*, long&)

__NSCFArray     0x5f838b0   32  AudioToolbox    SimAggregateDevice::SimAggregateDevice(__CFString const*, __CFString const*, long&)

any help would be awesome and thank you from... yes... a newbie.

Answer 1

Firstly, I think you're running your app on the simulator - you shouldn't.

Or rather, never use the simulator to test for memory allocations, leaks, etc. You should always run it on the device itself.

I think if you run it on the device you'll still see this leak (well, you'll see something similar), if you google the various things you're getting back you'll see other people having this problem. It appears as if there are some small leaks within the framework itself, which is something outside of your control. I'd just leave them be.

Answer 2

Also try the static analysis build. That will often reveal retain/release mismatches and general leaks. You can run it with Cmd+Shift+A (I think).