Thread 1: EXC_BAD_ACCESS (code=1, address=0xf00000c)

Question

I have problem with Thread 1: EXC_BAD_ACCESS (code=1, address=0xf00000c) and I don't know how to resolve it. It appeared when I change some object in core date and save it and I try to pop this controller to parent. This error is in main() with retVal. here is some code

        int retVal;
    @try {
        retVal =  UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
           */\ error is here**
    }
    @catch (NSException *exception) {
        NSLog(@"%@", [exception callStackSymbols]);
        @throw exception;
    }
    return retVal;

After re-runing app all my changes are in core data. What is more this problem is only on iOS 7. iOS 6.1 is ok.

Does someone have idea how to resolve it?

Can you attach the full stack trace here? It's unlikely that the error is in `main()`, it's more likely somewhere deep in your code. You can also try running your application in Instruments with the "Zombies" trace template, which should help you track down the object that's causing problems. — Craig Otis, Oct 04 '13 at 14:20
I *promise* you, the error isn't in `main()` that's just where the debugger is dumping you after everything else unwinds. — ipmcc, Oct 04 '13 at 14:20
`EXC_BAD_ACCESS` is a hard crash and cannot be caught via `@catch`. — bbum, Oct 04 '13 at 15:32
This will also be a case sometimes when you try to do some UI things on background thread. I was showing an alert from background thread. — Vivek Sinha, Jun 23 '17 at 11:48
If your issue is with `CoreData`'s `NSMAnagedContext.save()`method. I recommend **saving the context from within the perform block**, to make sure all data needed by CoreData will be still available — marcelosalloum, Apr 18 '19 at 12:48

score 23 · Answer 1 · answered Nov 09 '19 at 06:04

23

I just had the exact same problem.

Looked here and found nothing so I started backtracking until I thought, maybe I should try Clean Build Folder

I was glad it was as easy as CLEAN BUILD FOLDER!!!

Product- Clean Build Folder(⇧ ⌘ K)

answered Nov 09 '19 at 06:04

Superlative

514
1
4
14

The only solution for me; in my project the problem was that the EXC_BAD_ACCESS has been raised when I did changes in my cocoapod in development in local environment; I presume that Xcode doesn't get changes but give no errors at build time. So, clean build folder helps. thanks – ricky.tribbia Jul 31 '20 at 07:13

Peter DeWeese · Accepted Answer · 2013-10-04T14:55:27.727

20

As a comment said this error is likely to be deep in your code. If the culprit is a zombie, the easiest way to find it is to run it (preferably in the latest Xcode, currently Xcode 5, as it has been improved) in profiler and choose "Zombies". When it fails, you can see the history of everything that has happened to the object.

Also, set an exception breakpoint. You may get a break when the error happens instead of in main, where the exception gets passed up.

edited Oct 04 '13 at 14:55

answered Oct 04 '13 at 14:49

Peter DeWeese

18,141
8
79
101

Profiler doesn't tell which object is the zombie. Is there a wmdc that does this? – user4951 Oct 11 '13 at 06:59
It should tell you with a notification when it breaks on a zombie. Are you using Xcode 5? – Peter DeWeese Oct 11 '13 at 14:16

score 13 · Answer 3 · edited May 09 '16 at 13:32

13

I resolved this problem with "Zombies" and the problem was with [UIScrollView(UIScrollViewInternal) _notifyDidScroll]

I added

- (void)dealloc {

  self.tableView.delegate = nil;

}

This problem was only in iOS 7.

Thanks for help!

edited May 09 '16 at 13:32

Hafiz Ismail

3,195
1
25
21

answered Oct 07 '13 at 11:26

user2375706

705
2
8
14

1

Great! Make sure to select an answer. – Peter DeWeese Oct 07 '13 at 14:39
what does a scrollview has to do with your table views delegate. I'm confused – DevilInDisguise Mar 27 '15 at 23:53
1

UITableView is a subclass of UIScrollView, and so the UITableViewDelegate inherits the UIScrollViewDelegate methods as well (i.e. notifyDidScroll). – HGDev Apr 03 '15 at 16:13

score 11 · Answer 4 · edited Nov 07 '19 at 11:31

I have resolve this issue only by debugging the source code and re-analyze my logic.

Below are some reference that help me lot.

EXC_BAD_ACCESS means that message was sent to a point in the memory where there’s no instance of a class to execute it. Thus “bad access”.

You will get EXC_BAD_ACCESS in 3 cases:

An object is not initialized
An object is already released
Something else that is not very likely to happen

That’s already a good starting point. Start using the debugger, if you recently added a new object to the class you’re working on, put a breakpoint at the line before the freshly added object is used for the first time and check the values in the debugger.

What’s happening most though is that you will be sending a message to an overreleased object – i.e. object that is gone from the call stack. In this cases everything (and indeed everything) you will get in the console will be just :EXC_BAD_ACCESS

This is because the object is gone, there is no information what class was it, or what source file or anything else.

Please try to avoid using zombies for this.

What that last part means "avoid using zombies"?? – Wahab Khan Jadon May 15 '22 at 20:10 — Wahab Khan Jadon, May 15 '22 at 20:10

score 3 · Answer 5 · answered Jan 21 '16 at 09:14

EXC_BAD_ACCESS means there is no instance of a class to execute it.

There are 2 or more possibilities:

An object is not initialized
An object is already released

Please debug application carefully and analyze each object carefully. That might solve your issue.

score 1 · Answer 6 · edited Sep 18 '14 at 00:03

1

I solved the same problem by finding out that the name of one of my NSString variables had the same name as one of the frameworks' class variables. Took seconds to change the name a little and problem disappeared.

With such a huge number of class variables in frameworks, it is very likely that once in a while, every programmer just by coincidence names some variable in his class exactly the same as one used somewhere in framework classes. So it doesn't have to be Xcode bug in most cases.

edited Sep 18 '14 at 00:03

AstroCB

12,337
20
57
73

answered Sep 17 '14 at 23:28

Stan

11
1

5 years after you I encountered the same problem :P – J. Doe Jul 11 '19 at 18:37

score 1 · Answer 7 · answered Sep 07 '18 at 04:49

1

In my case, I was using third-party library and I forgot to set custom-class name in Storyboard Identity Inspector

answered Sep 07 '18 at 04:49

Nay

677
1
8
14

score 0 · Answer 8 · answered Jul 05 '16 at 13:07

0

And there may be another issue which I faced today: I had a mutable dictionary with a non-object entry try. There was a code snippet with adding a BOOL value to the dictionary. So no wonder that I got this error =).

answered Jul 05 '16 at 13:07

AOY

355
3
22

score 0 · Answer 9 · answered Mar 01 '21 at 13:56

0

In my case it was trying to log an Int32 with %s in print statement

answered Mar 01 '21 at 13:56

Ivan

1,254
12
25

Shaybc · Answer 10 · 2022-11-11T13:12:09.237

in my view this is the equivalent of every other language NullPointerException,

but unlike other languages there are no hellping pointers (class name / method or line of the occurrence / god forbid a Stacktrace),

so the only thing i could do to solve it fast is to start printing main functions and views, (a very primitive solution),

create a swift: Debug.swift
add this function into Debug.swift:

public func trace(_ message: String = "", file: String = #file, function: String = #function, line: Int = #line)
{
    print("****  \(file).\(function)[\(line)]: \(message)")
}

then you can use it like this:

trace("initializing")

to use it inside a var do this:

let _ = trace("initializing")

this should print something similar to this:

****  /path/to/my/file/MyFile.swift.someFunc()[18]: initializing

this is how i started adding debug lines to gain some flow record, so next time i have a EXC_BAD_ACCESS i will have a clue where the problem leis

don't forget to disable the prints during production deployment

Thread 1: EXC_BAD_ACCESS (code=1, address=0xf00000c)

10 Answers10

Linked