ansaurus

Question

Activity has leaked window that was originally added

Answer 1

+4 A:

You're trying to show dialog after you're exit activity ( your thread came back ). THere are like 5 question with same thing in the last two weeks

Alex Volovoy 2010-05-17 15:54:21

Answer 2

+2 A:

The solution is to call dismiss() on the Dialog you created in viewP.java:183 before exiting the Activity, e.g. in onPause().

Views have a reference to their parent Context (taken from constructor argument). If you leave an Activity without destroying Dialogs and other dynamically created Views, they still hold this reference to your Activity (if you created with this as Context: like new ProgressDialog(this)), so it cannot be collected by the GC, causing a memory leak.

molnarm 2010-05-17 18:50:08

Answer 3

A:

If you are using AsyncTask, probably that log message can be deceptive. If you look up in your log, you might find another error, probably one in your doInBackground method of your AsyncTask, that is making your current Activity to blow up, and thus once the AsyncTask comes back.. well, you know the rest. Some other users already explained that here :-)

ggomeze 2010-07-20 18:23:38

Answer 4

A:

@ggomeze exactly,I used AsyncTask,and got the error msg,but it has nothing to do with Dialog,The real reason is that in doInBackground I set a view's property instead of in the origin view that created the view

(the ex shows :`android.view.ViewRoot$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views`).

Thanks :)

DiveInto 2010-08-27 07:43:03

Answer 5

A:

You can get this exception by just a simple/dumb mistake, by (for example) accidentally calling finish() after having displayed an AlertDialog, if you miss a break call statement in a switch statement...

   @Override
   public void onClick(View v) {
    switch (v.getId()) {
        case R.id.new_button:
            openMyAlertDialog();
            break; <-- If you forget this the finish() method below 
                       will be called while the dialog is showing!
        case R.id.exit_button:
            finish();
            break;
        }
    }

The finish() method will close the Activity, but the AlertDialog is still displaying!

So when you're staring intently at the code, looking for bad threading issues or complex coding and such, don't lose sight of the forest for the trees. Sometimes it can be just something as simple and dumb as a missing break statement. :)

Adrian Romanelli 2010-10-08 08:48:19

Answer 6

A:

i get the same error but i do not understand where to dismiss my progress dialog. (as molnarm is describing it)

here the code:

public class sammlung extends Activity {
/** Called when the activity is first created. */
TextView text1;
ProgressDialog pd;
@Override
public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.test);
    text1 = (TextView) findViewById(R.id.TextView01);

    pd = ProgressDialog.show(this, "", "Lädt...", true);

    new Thread(){
        public void run(){
            download();
            pd.dismiss();
            }
        }.start(); 
}

The download class is just downloading some data from a website. this part works but it crashes with the progress dialog. i start the app see the progress dialog and after a while(i think after the download is done) the error apperears.

cesar009 2010-10-17 17:36:40

ansaurus

tags:

views:

answers:

Activity has leaked window that was originally added

related questions