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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T05:51:05+00:00 2026-05-14T05:51:05+00:00

I am getting the NSConcreteData leaked object while testing the leaks in the instruments.It

  • 0

I am getting the NSConcreteData leaked object while testing the leaks in the instruments.It showing in the parser,

- (void)parseXMLFileAtURL:(NSURL *)URL
{
  [urlList release];
  urlList = [[NSMutableArray alloc] init];

  myParser = [[NSXMLParser alloc] initWithContentsOfURL:URL] ;// it showing this line as leaking


  [myParser setDelegate:self];
  [myParser setShouldProcessNamespaces:NO];
  [myParser setShouldReportNamespacePrefixes:NO];
  [myParser setShouldResolveExternalEntities:NO];
  [myParser parse];
  [myParser 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-14T05:51:05+00:00Added an answer on May 14, 2026 at 5:51 am

    That is extremely unlikely to be the source of the leak, since you’re not using NSData around there, like, at all. You might want to see where that URL comes from.

    Edit: It might be nice if you edit your original post with the new information, but nonetheless; insofar as I can see, that code shouldn’t leak. This kind of error can be tedious to track down; and the NSConcreteData might be a red herring, but I’m thinking you should look for your uses of NSData throughout your project.

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

Sidebar

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.