Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5940983
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T16:02:44+00:00 2026-05-22T16:02:44+00:00

I am stuck on a EXC_BAD_ACCESS crash within my dealloc of a table view

  • 0

I am stuck on a EXC_BAD_ACCESS” crash within my dealloc of a table view controller. The crash occurs when releasing an NSMutableArray that was given a retain property. I have a second NSMutableArray that was also given a retain property, but it’s release does not cause a crash. Please take a look at the following code to see if I am overlooking something about memory management. Thanks.

In my header file, I have the following:

@interface selectSourcesTableViewController : UIViewController  <UITableViewDelegate, UITableViewDataSource> {
    NSMutableArray *selectedNames;
    NSMutableArray *selectedAvailability;
}

@property (retain, nonatomic)   NSMutableArray  *selectedNames;
@property (retain, nonatomic)   NSMutableArray  *selectedAvailability;

In my implementation, I have the following:

@implementation selectSourcesTableViewController
@synthesize selectedNames;
@synthesize selectedAvailability;

- (void)viewDidLoad {

    NSArray *names = [selectedSourceFileContent objectForKey:@"selectedNames"];
    selectedNames = [[NSMutableArray alloc] initWithObjects: nil];

    NSArray *availability = [selectedSourceFileContent objectForKey:@"selectedAvailability"];
    selectedAvailability = [[NSMutableArray alloc] initWithObjects: nil];

    for (int i=0; i < [names count]; i++) {
        NSString *aName = [names objectAtIndex:i];
        [selectedNames addObject: aName];
        NSString *anAvailability = [availability objectAtIndex:i];
        [selectedAvailability addObject: anAvailability];
    }
}


- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath {

    UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier: kCellIdentifier];

...

    for (int i=0; i < [selectedNames count]; i++) {
        if ([contentForThisRow isEqualToString:[selectedNames objectAtIndex:i]]) {
            cell.accessoryType = UITableViewCellAccessoryCheckmark;
        }
    }
}

- (void)dealloc {
    [super dealloc];
    [selectedNames release];
    [selectedAvailability release];
}

The code shown above shows the only uses of these two arrays.

So, nothing bad happens when selectedNames is released, but I get a EXC_BAD_ACCESS crash when selectedAvailability is released.

One last observation. There is no crash the very first time I run this code after launching xcode. Thereafter, it crashes every time I rerun the app.

Any thoughts?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T16:02:45+00:00Added an answer on May 22, 2026 at 4:02 pm
    [super dealloc]
    

    needs to be called last, not first, in your own dealloc method.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm a bit stuck repairing a faulty table (on Hbase 0.92.1-cdh4.0.0, Hadoop 2.0.0-cdh4.0.0) There
I am getting an interesting crash that I can never seem to replicate on
I've been stuck on this EXC_BAD_ACCESS error 2 days now. I have a reloadAnnotations
Ok I've got a dreaded EXC_BAD_ACCESS that I can't seem to track down but
I have ParentViewController that allocates ChildViewController , pushes it onto controller stack and releases
I have a modal view controller which is crashing when it dismisses itself. The
I am getting the error EXC_BAD_ACCESS on the line CGContextClearRect(c, self.view.bounds) below. I can't
I am stuck. I don't know why its being crashing in the dealloc scope
Stuck on KVCs in Obj-C again. I am wanting to use KVC to find
Been stuck on this for ages. Currently learning Django and done some bits on

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.