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 4084454
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T18:26:30+00:00 2026-05-20T18:26:30+00:00

I would like to ask about memory management with regards to MKReverseGeocoder , prior

  • 0

I would like to ask about memory management with regards to MKReverseGeocoder, prior to iOS4.3 I had been using the code below, allocing MKReverseGeocoder and then releasing it in either reverseGeocoder:didFindPlavemark or reverseGeoCoder:didFailWithError as appropriate.

However with iOS4.3 I am getting EXC_BAD_ACCESS and it seems to be coming from the release in reverseGeocoder:didFailWithError. I would very much appreciate it if someone could point me in the right direction, could I use autoRelease, would that alloc the geoCoder to hang around long enough for the delegate to do its work?

// ALLOC & START
MKReverseGeocoder *myGeocoder = [[MKReverseGeocoder alloc] initWithCoordinate:[lastGoodLocation coordinate]];
[myGeocoder setDelegate:self];
[myGeocoder start];

.

// DID FIND
- (void)reverseGeocoder:(MKReverseGeocoder *)geocoder didFindPlacemark:(MKPlacemark *)placemark {
    NSLog(@"GEOCODE: didFindPlacemark");
    [self createLocation:placemark];
    [geocoder release];
}

.

// DID FAIL
- (void)reverseGeocoder:(MKReverseGeocoder *)geocoder didFailWithError:(NSError *)error {
    NSLog(@"GEOCODE: didFailWithError");
    [self createLocation:nil];
    [geocoder release];
}
  • 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-20T18:26:31+00:00Added an answer on May 20, 2026 at 6:26 pm

    After a little searching, I think the solution might be to setup an iVar to hold the MKReverseGeocoder. This way I can use autorelease whilst still being sure that the iVar will hold onto the geoCoder until the next time the iVar is set. Interestingly enough the code above only produces an EXC_BAD_ACCESS from reverseGeocoder:didFailWithError, not from reverseGeocoder:didFindPlacemark. I also checked the retain counts (yes I know its not reliable but I wanted to look) and before the release (that crashes) both methods report a retain count of 1. The only thing I can guess is that the geocoded object might still be being used somewhere when I do the release. It also feels messy allocing in one method and releasing using a pointer from the callback.

    @property(nonatomic, retain)MKReverseGeocoder geoCoder;
    

    .

    [self setGeoCoder:[[[MKReverseGeocoder alloc] initWithCoordinate:coord] autorelease]];
    [[self geoCoder] setDelegate:self];
    [[self geoCoder] start];
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

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.