[EMAIL PROTECTED] wrote:
>> if (internalStringCode != NULL) {
>> return (String) this.stringList.get(internalStringCode);
>> }
>>
>> If you have traced your code in the debugger and found that this is not
>> used,
>> and instead the String constructor is called as you describe, it would be
>> helpful if you could provide a test case.
>
> No, it was done by static analysis with my eyeballs.
>
> It seems I made a mistake. I should have asked about it on uima-users
> instead of making a request in Jira. I'm sorry to have wasted your time. :-(
>
>
> Greg
>
No problem. We love to hear about out-of-memory problems ;-)
Seriously, if you think your memory problems are UIMA-related,
or even if not, feel free to post more.
I don't know what JVM you are using, but you can get the IBM
JVMs to create a heap dump on OutOfMemoryErrors. You can then
use a variety of tools to look at the state of the heap at the
time of the crash. This has proved to be an invaluable tool
for me on several occasions, chasing memory leaks. Let me know
if you need more info.
--Thilo
