ShareKit/Twitter memory leak

483 Views Asked by At

I've got a problem - I'm using ShareKit 2.0, and while I'm testing on iOs 5.0.1 I get some memory leaks when I'm trying to share on Twitter. To be exact, at the moment when native ios5 twitter window pops-up, and when i hit "send". The problem seems to be in TWSession. When I'm testing on iOS 4.3, and using custom sharekit twitter window there are no leaks. Any idea on how to fix it? Will this be an issue on the approval process? I'm not using ARC btw.

2

There are 2 best solutions below

2
On BEST ANSWER

I have never heard of an app being rejected for a small memory leak. Also, unless the whole point of your app is to send tweets, users are unlikely to send enough tweets to make a big difference (annoying as any leak is).

0
On

What I have also found the codes caused leaks are as the followings:

Leaked Object # Address Size Responsible Library Responsible Frame NSMallocBlock,1 0xf641c50 32 Bytes Twitter -[TWInFlightSessionCallInfo setRemoteCall:] TWInFlightSessionCallInfo,1 0xf676380 16 Bytes Twitter -[TWSession emptyCallInfo] Malloc 16 Bytes,1 0xf6457c0 16 Bytes Twitter -[TWSession recordAndIssueCallInfo:] Malloc 128 Bytes,2 < multiple > 256 Bytes libdispatch.dylib dispatch_queue_create$VARIANT$up NSLock,1 0xf64b450 64 Bytes Twitter -[TWSession init] TWSession,1 0xf62c3e0 32 Bytes Twitter -[TWTweetComposeViewController session] NSMutableArray,1 0x2c8540 32 Bytes Twitter -[TWSession init] NSMallocBlock,1 0x1084ebb0 32 Bytes Twitter -[TWInFlightSessionCallInfo setRemoteCall:]