Re: Tracking down unwanted object retentions that are eating memory -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Tracking down unwanted object retentions that are eating memory
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
Date: Fri, 19 May 2006 09:03:22 -0700
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

"Joe Sam Shirah" <jshirah@xxxxxxxxxxxxx> wrote:

Sounds like one of those premature optimization things.

Not really; it's just that the intern() had been there forquite a while, whereas the truncation (and the need forit) is a comparatively recent change. And until I actuallylooked it up, I wasn't even aware of what intern() does (Iwasn't the one who put it there).


--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.