Memory leaks and crashes due to Internet connection not available about bump-api-ios

[venkatd]

I am also having the same issue. When the internet is disconnected the memory usage for libBump skyrockets...

[tewks]

Thanks for the reports. We'll investigate and issue a fix.

[himanshur]

Any update on this? Even I am facing this issue. The memory usage goes incredibly high if network connectivity is absent when bump is configured, resulting in the app crashing in a matter of few seconds..

[himanshur]

Hi tewks. Is there any fix available for this? are there any plans at all to fix this. If not, I might have to dump Bump, as its unusable right now..

[johndpope]

I'm using this code in mean time in main.m file

#import <UIKit/UIKit.h>
#import "AppDelegate.h"
#import <sys/signal.h>

void SigPipeHandler(int s);

void SigPipeHandler(int s)
{
NSLog(@"We Got a Pipe Single :%d____________",s);
}

int main(int argc, char *argv[])
{
@autoreleasepool {
signal(SIGPIPE, SigPipeHandler);
// signal(SIGPIPE, SO_NOSIGPIPE);
return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
}
}

[johndpope]

Pretty simple to recreate this problem - just start phone up in airline mode and watch the memory blow out.
Any ETA on a fix for this?

[johndpope]

Is there a way you can provide a method to tear down the entire singleton class and destroy BumpClient?
That would at least provide us a way to bandaid this situation based off the network availability - other wise this is not production worthy code.

[johndpope]

/// if using ARC set this -fno-objc-arc

@interface DestroyBump : NSObject
+(void)deallocateNastyMemoryLeakUntilBumpSdkIsFixed;

@EnD

#import "DestroyBump.h"
#import "BumpClient.h"
#import <objc/runtime.h>

@implementation DestroyBump

+(void)deallocateNastyMemoryLeakUntilBumpSdkIsFixed{
BumpClient *bc = [BumpClient sharedClient];
[bc disconnect];
[bc setChannelConfirmedBlock:nil];
[bc setDataReceivedBlock:nil];
[bc setConnectionStateChangedBlock:nil];
[bc setBumpEventBlock:nil];
[bc release];
}

@EnD

[george-apostu]

Same issue here. Any update?

[tewks]

Fixed in 3.1