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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T07:18:32+00:00 2026-05-23T07:18:32+00:00

i had a problem with memory leak in this below code , potential leak

  • 0

i had a problem with memory leak in this below code ,
potential leak of an object in line 39,

and here line 39 is ,[self alloc] init];

+ (UploaderThread *)sharedUploaderThread {
    @synchronized(self) {
        if (_sharedUploaderThread == nil) 
        {
            [[self alloc] init];

        }
    }
    return _sharedUploaderThread;
}

plz help me , wer i did the mistake

  • 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-23T07:18:33+00:00Added an answer on May 23, 2026 at 7:18 am

    You are not assigning the value to _sharedUploaderThread. Do

    _sharedUploaderThread = [[self alloc] init];
    

    Since you were not assigning the value, you were leaking.

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

Sidebar

Related Questions

I appear to have a memory leak in this piece of code. It is
I've had this problem many times before, and I've never had a solution I
I've had this problem a couple of times. Let's say I want to display
I had an odd problem today when I was trying to serialize an object.
in a previous question i had a problem in some code,, after revealed, i
I had a problem that was partially solved. To explain it quickly : I
I had a problem with committing changes after merging two branches of my project
I recently had a problem during the deployment of a windows service. Four computers
I recently had a problem in my app where some of the subviews I
Today I had the problem that I couldn't delete a folder because it was

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.