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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 10, 20262026-06-10T09:11:14+00:00 2026-06-10T09:11:14+00:00

Consider the following scenario: An object myObj is instantiated locally in some function myFunc

  • 0

Consider the following scenario:

  • An object myObj is instantiated locally in some function myFunc.
  • myObj starts a thread someThread which runs some background task, e.g. reads from a socket.
  • myFunc then returns, causing myObj to be dereferenced.

Under normal circumstances, the JVM would just garbage-collect myObj. However, if someThread is still running, would this still be the case?

I understand that someThread itself would not be GC’d as long as it is still running, but in my code it also needs to access values stored in myObj, so it is important that I make sure myObj persists while it is still running.

  • 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-06-10T09:11:16+00:00Added an answer on June 10, 2026 at 9:11 am

    An object is only eligible for garbage collection if it has no references to it. You say that someThread needs to access values stored in myObj, which means it must have a reference to myObj. This means that myObj is not eligible for garbage collection unless someThread is also eligible.

    You can guarantee that an object will never be garbage collected from underneath you so this, for example, is perfectly safe:

    void foo() {
        final Object something = new String("I'm alive!");
        new Thread() {
            public void run() {
                try {Thread.sleep(10000);} catch (InterruptedException e) {}
                System.out.println(something);
            }
        }.start();
    }
    

    something is referenced by the anonymous thread so it is not eligible for garbage collection until the anonymous thread is done.

    More specifically for your example, this is also safe:

    void foo() {
        new ThreadStartingObject("I'm alive!");
    }
    
    class ThreadStartingObject {
        private String message;
    
        public void ThreadStartingObject(String msg) {
            this.message = msg;
            new Thread() {
                public void run() {
                    try {Thread.sleep(10000);} catch (InterruptedException e) {}
                    System.out.println(message);
                }
            }.start();
        }
    }
    

    The anonymous inner class representing the thread has an implicit reference to the outer this, i.e. the instance of ThreadStartingObject. That reference prevents garbage collection.

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

Sidebar

Related Questions

Let's consider the following scenario: a function which can generate code colors from white
consider the following scenario: I have a storyboard-based app. I add a ViewController object
Consider the following scenario which I'm due to find myself in shortly: You're to
And wait, don't rush to answer java.util.Date, consider the following scenario. Person object having
Consider the following scenario. I have a method which returns ISomething , but it
Consider following scenario: I have RESTful URL /articles that returns list of articles user
Consider the following scenario: /** * A sample interface. */ public interface MyInterface {
Consider the following scenario We have a simple database that involves two entities: user
Consider the following scenario . I have an array of numbers: [ 1,2,3,4 ]
consider the following code scenario: <?php //widgetfactory.class.php // define a class class WidgetFactory {

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.