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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T00:55:39+00:00 2026-05-22T00:55:39+00:00

Memory need to be release for alloc, retain and copy. My question is for

  • 0

Memory need to be release for alloc, retain and copy. My question is for following situation where I retain the UIImage property, but it was autorelease by the function of imagedNamed. Should I still release following variable?

@property (nonatomic, retain) UIImage *image;
self.image = [UIImage imageNamed:@"image.png"];

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-22T00:55:40+00:00Added an answer on May 22, 2026 at 12:55 am

    Yes you have to release image since you retained it.

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

Sidebar

Related Questions

As is common knowledge, calls to alloc/copy/retain in Objective-C imply ownership and need to
@property (nonatomic,copy) NSString *orginalString; .. NSString *tmpString =[[NSString alloc] init]; self.orginalString=tmpString; [tmpString release]; NSString
Do I need to release a Core Foundation objects to clear up memory? And
I know the basic principles about memory management (retain count, autorelease pools etc) in
I have several medium-sized data sets in-memory that I need to be able to
I can never remember the number. I need a memory rule.
I need to implement an in-memory tuple-of-strings matching feature in C. There will be
I need to know when the memory will be allocated for a particular program.
I need to do some memory profiling of a .NET Framework application. Should I
I need to configure Tomcat memory settings as part of a larger installation, so

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.