From this backtrace it looks like you might be trying to perform UI operations
someplace other than on the main queue, which would cause problems. I'd start
by checking whether you have:
-Any dispatches to a background queue that might need a dispatch_async to the
main queue.
-Any observer
Thanks Mike.. I will try that and check for memory leaks in my app
On Mon, Jun 22, 2015 at 2:38 PM, Mike Abdullah mabdul...@karelia.com
wrote:
Have you experimented with passing something bigger than CGRectZero for
the web view’s initial size? Maybe it’s freaking out over that.
Some googling
Have you experimented with passing something bigger than CGRectZero for the web
view’s initial size? Maybe it’s freaking out over that.
Some googling also suggests that the bbadbeef code can mean WebKit couldn’t
allocate enough memory. Maybe you’re using too much memory in your app in total?
Here is my viewDidLoad method:
EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0xbbadbeef
- (void)viewDidLoad {
[super viewDidLoad];
[self setTitle:[self.parameters_ get:@title]];
whiteBGLayer = [[CALayer alloc] init];
[whiteBGLayer setBackgroundColor:[UIColor
