×
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.
Hi Brad,
Like I said, all variables are declared as standalone, and
LR is set on once the app is complete. so I would think
any memory that is used in the Java app would be fine.
I don't understand why it matters if the variables are standalone. I don't
think data structures are any more dangerous than standalone fields... or
do you mean that they're not BASED?
I also don't see why LR matters at all. Unless you're running in the
default activation group, LR has no impact on whether the program remains
activated.
So to me, either sounds like some obscure OS/JVM issue, or
a bug in the Java code where it's reusing memory without
"resetting" it.. or reinitializing it.
It could be. Though, the more I think about it, the more I think about
how easy it would be for an unexperienced programmer to make a mistake
like this if they're calling the JNI APIs.
Might be worth looking at their code carefully...
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.