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

  • SEARCH
  • Home
  • 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 6934245
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 27, 20262026-05-27T11:56:06+00:00 2026-05-27T11:56:06+00:00

I am getting a leak on the helper.offlineQueue line where I alloc a NSOperationQueue

  • 0

I am getting a leak on the helper.offlineQueue line where I alloc a NSOperationQueue object. The problem is, I am not quite sure where to release it in this method…

+ (void)flushOfflineQueue
{
    // TODO - if an item fails, after all items are shared, it should present a summary view and allow them to see which items failed/succeeded

    // Check for a connection
    if (![self connected])
        return;

    // Open list
    NSMutableArray *queueList = [self getOfflineQueueList];

    // Run through each item in the quietly in the background
    // TODO - Is this the best behavior?  Instead, should the user confirm sending these again?  Maybe only if it has been X days since they were saved?
    //      - want to avoid a user being suprised by a post to Twitter if that happens long after they forgot they even shared it.
    if (queueList != nil)
    {
        SHK *helper = [self currentHelper];

        if (helper.offlineQueue == nil)
            helper.offlineQueue = [[NSOperationQueue alloc] init];      

        SHKItem *item;
        NSString *sharerId, *uid;

        for (NSDictionary *entry in queueList)
        {
            item = [SHKItem itemFromDictionary:[entry objectForKey:@"item"]];
            sharerId = [entry objectForKey:@"sharer"];
            uid = [entry objectForKey:@"uid"];

            if (item != nil && sharerId != nil)
                [helper.offlineQueue addOperation:[[[SHKOfflineSharer alloc] initWithItem:item forSharer:sharerId uid:uid] autorelease]];
        }

        // Remove offline queue - TODO: only do this if everything was successful?
        [[NSFileManager defaultManager] removeItemAtPath:[self offlineQueueListPath] error:nil];

    }
}

Thanks!

  • 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-27T11:56:07+00:00Added an answer on May 27, 2026 at 11:56 am

    I expect you should just do:

    helper.offlineQueue = [[[NSOperationQueue alloc] init] autorelease];
    

    The SHK object itself should be retaining the queue and will release it when it is done. The reference you are holding due to the alloc can be released immediately.

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

Sidebar

Related Questions

I am getting a leak on this line and I'm not sure why... weather.condition
I'm getting memory leak problem in this code: UIImage myImage1 = [[UIImage alloc] initWithData:[NSData
I getting the leak in this method even the allocated nsstring is released. Now
I am getting the leak at this line in below code NSData *returnData =
I am getting leak at [pool release]; My code here is: #pragma mark UISearchBarDelegate
I'm getting a memory leak with instruments in a class that I've created. This
I'm getting an analyser leak, however this is the same code i'm using elsewhere
I'm getting an instruments Memory Leak with this iPhone 3.0 SDK code. I'm using
I am getting another memory leak in a non-void instance method that returns a
In my pgm, i am getting a leak warning in this segment. -(NSMutableArray *)filterArrayForBank:(NSMutableArray

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.