Do anyone know what this memory leaks are?

[Johanovski]

Hi there!

I'm working with Instruments on my app, seeking leaks, object allocations, etc and, after cleaning my own leaks, I still found some which are not mine. I'm not sure if they are real leaks or just an Instruments error because I don't know where they came from but I'm sure they don't came from my own code, so it's strange... I found 2 types of leaks:

************************************************** **********
Leaked Object: GeneralBlock-16
#: 14
Address: < multiple > --> Example: 0x258de0
Size: 224 Bytes (16 Bytes each one)
Responsible Library: GraphicsServices
Responsible Frame: PurplePushEvent

Leaked Object: GSEvent
#: 6
Address: <multiple > --> Example: 0x258d60
Size: 768 Bytes (128 Bytes each one)
Responsible Library: GraphicsServices
Responsible Frame: CreateWithEventRecord
************************************************** **********

Does anyone know what can be happening? What can I do to solve this leaks? Are them a real problem or just a minor issue?

Thanks in advance for your help!

[materialised]

Originally Posted by Johanovski

Hi there!

I'm working with Instruments on my app, seeking leaks, object allocations, etc and, after cleaning my own leaks, I still found some which are not mine. I'm not sure if they are real leaks or just an Instruments error because I don't know where they came from but I'm sure they don't came from my own code, so it's strange... I found 2 types of leaks:

************************************************** **********
Leaked Object: GeneralBlock-16
#: 14
Address: < multiple > --> Example: 0x258de0
Size: 224 Bytes (16 Bytes each one)
Responsible Library: GraphicsServices
Responsible Frame: PurplePushEvent

Leaked Object: GSEvent
#: 6
Address: <multiple > --> Example: 0x258d60
Size: 768 Bytes (128 Bytes each one)
Responsible Library: GraphicsServices
Responsible Frame: CreateWithEventRecord
************************************************** **********

Does anyone know what can be happening? What can I do to solve this leaks? Are them a real problem or just a minor issue?

Thanks in advance for your help!

Are you testing on the device and not the simulator? Memory usage on the device is different to the simulator.

[Johanovski]

I'm testing on the device with 3.0 OS, no problems in the simulator... I don't know what to do because these leaks have no sense for me!

[finefin]

This post is quite old. But... because I recently had the same problem and this thread appears on 3rd place on google I will answer it here:

What I found out is that the rising GSEvent-memory allocations are caused by the accelerator in conjunction with an enabled NSZombie variable.

The solution is to kill the NSZombie!
(you should do that before releasing the app, anyway)

hope that helps.

[krish]

Originally Posted by finefin

This post is quite old. But... because I recently had the same problem and this thread appears on 3rd place on google I will answer it here:

What I found out is that the rising GSEvent-memory allocations are caused by the accelerator in conjunction with an enabled NSZombie variable.

The solution is to kill the NSZombie!
(you should do that before releasing the app, anyway)

hope that helps.

How can I achieve that? Please help me.

[plug-in]

I've the same issue, disabled NSAutoreleaseFreedObjectCheckEnabled, NSZombieEnabled and NSDebugEnabled and leaks disappeared.

[krish]

Originally Posted by plug-in

I've the same issue, disabled NSAutoreleaseFreedObjectCheckEnabled, NSZombieEnabled and NSDebugEnabled and leaks disappeared.

Where did you disable it?

[finefin]

look for "Executables" in your project overview.
find your executable file and press cmd+i
click the "Arguments" tab
see if there's anything listed under "Variables to be set..."

more info: CocoaDev: NSZombieEnabled

[plug-in]

Yes, finefin is right.
Just click on "plus" in this section and type "NSZombieEnabled" and value "NO". Same for other variables.