Comments on: String and memory leaks

By: vibram five fingers kso shoes

vibram five fingers kso shoes — Sat, 03 Jul 2010 04:11:03 +0000

Women's vibram five fingers kso shoes Gray Pink Shoes can keep your feet in the freest condition,just as if your were barefooted. vibram five fingers kso shoes is made of the best and proper materials,so you don't need to doubt of its comfort with so thin sole and upper. Gray match with a dreamlike and romantic color,pink vibram five fingers kso shoes is very consistent with the style of young girls.In this busy and tense times,people need relax without any fetter.

By: admin

admin — Tue, 03 Nov 2009 16:32:14 +0000

By saying ” your code will invoke getPageTitle() method many times” I meant invocation with different URLs to get different pages. Since URLs are different the page content is also different and there is no sharing of strings between requests.

Even if you would execute this method with the same parameter 1000 times, since the content is downloaded from the web you probably would get different string objects that would have the same content, but did not share an char array (unless getPageContent(pageUrl) implements some caching mechanism or interns the results).

By: z

Tue, 03 Nov 2009 16:13:48 +0000

If your code will invoke getPageTitle() method many times you may find out that you have stored only a thousand titles and already you are out of memory!! Scary, right?

not really. as u mentioned u have only one 100k char array, so if u run out of memory that’s not bckz u invoked 1000 times getPageTitle().
once u have 1 String pointing at the title u already have a live reference, so there should not be a big difference 1 or 1000 references.

By: z

Tue, 03 Nov 2009 16:08:34 +0000

>pls help me understand if String object is >garbage collected?
>As far as I know String is stored in a pool >.therefore once created it cannot be garbage >collected?

if u define a variable like:
String z = “aaa”; // this value will be taken from String’s pool.
String z = new String(”aaa”); // here a new string object with value “aaa” will be created regardless of what u have in ur pool.

ps: afaik some of values from String’s global pool, will be GC-ed at some point.. but this is not smth u should care about.

By: A.Clark

A.Clark — Wed, 07 Oct 2009 10:14:53 +0000

Awesome ! Really appreicate your job !

By: Amit

Amit — Fri, 11 Sep 2009 17:31:52 +0000

A very good article.

By: Twitter Trackbacks for JavaBlogging » String and memory leaks [javablogging.com] on Topsy.com

Fri, 28 Aug 2009 16:57:04 +0000

[...] link is being shared on Twitter right now. @shauryashaurya said I love the tag line here: [...]

By: Shailendra

Shailendra — Thu, 30 Jul 2009 13:11:05 +0000

pls help me understand if String object is garbage collected?
As far as I know String is stored in a pool .therefore once created it cannot be garbage collected?

By: Kevin Jordan

Kevin Jordan — Wed, 29 Jul 2009 13:58:49 +0000

I’d probably use StringBuffer if I knew a String was going to be more than 1000 characters long. In fact, that’s probably the way to go for substring anyways if you don’t care about the original string being cached.

By: Tony Morris

Tony Morris — Wed, 29 Jul 2009 09:30:23 +0000

Java does so many things wrong, including java.lang.String. The issue here is the forced evaluation of the data structure. The forced evaluation is required since Java is a forcefully imperative language with no flexibility.

Functional Java has a lazy list (fj.data.Stream) data structure that will solve your problem. Take a look at the drop/take methods some time.

Better still, upgrade the language to a more practical one.