× 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.



I program PIC microcontrollers in my spare time in their native assembly
language as well as in C. I mention this so that you have a context to
put my notes into. I'm very familiar with programs dealing with memory
dynamically because I do it with the bare silicon.

C (and C++) have 2 well known problems:
- calculating with pointers (=> might cause blue screen effects, jumping to nowhere)
- allocating memory in a loop, without deallocating this memory anywhere (=> freezing programs)

Java came up a couple of years later and the designers of Java tried to remove both issues:
- there is no explicit pointer datatype, only named references (so you can't calculate with these)
- there is no dealloc operation, storage is freed automatically, when no reference is pointing to it. Setting a variable to null is sufficient to enable freeing of storage, if nobody else is pointing to it.
So Java is in my experience a language with a very easy concept of dealing with dynamic storage allocation, by far easier than C or RPG.

In your case (HSSF and a large spreadsheet) there is nothing in your programm beeing wrong, the two components you are using simply don't fit together. The problem of the OP is caused mainly by The RPG to Java JNI mix, Java doesn't have any chance to see which references the RPG part is holding, as long as the JNI part is explicit telling what's no longer needed. That's a very complicated situation, you would not have in a pure Java programm.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.