Memory leak problem

[sajithamol]

What is a memory leak problem?can anyone explain it with eg

[r035198x]

What is a memory leak problem?can anyone explain it with eg

For theoretical type questions, you are best to consult a text.

[JosAH]

What is a memory leak problem?can anyone explain it with eg

Using Java it's quite difficult to leak memory; here's an obvious example:

[code=java]
class Foo {
private static List<Foo> leak= new ArrayList<Foo>( );
public Foo() {
leak.add(this);
}
}
[/code]

Now keep on allocating Foo objects and keep forgetting about them. The garbage
collector is very willing to reap them but it can't: the 'leak' list still refers to them all.


kind regards,

Jos

[r035198x]

Using Java it's quite difficult to leak memory; here's an obvious example:

[code=java]
class Foo {
private static List<Foo> leak= new ArrayList<Foo>( );
public Foo() {
leak.add(this);
}
}
[/code]

Now keep on allocating Foo objects and keep forgetting about them. The garbage
collector is very willing to reap them but it can't: the 'leak' list still refers to them all.


kind regards,

Jos

Ha, your examples leave a lot to be desired.
So the Foo objects will only become eligible for collection when the Foo class is unloaded from the JVM?

[JosAH]

Ha, your examples leave a lot to be desired.
So the Foo objects will only become eligible for collection when the Foo class is unloaded from the JVM?

Yep, the Foo objects will stay there until the class itself is GC'd.

kind regards,

Jos