Subj : Any potential application issue when switching Rhino from interpreted
To   : netscape.public.mozilla.jseng
From : gordon
Date : Wed May 25 2005 08:36 pm

Hi Folks,

I am troubleshooting an (old) application that uses Rhino 1.5 R1 and 
that is experiencing OutOfMemoryErrors because Rhino is causing the 
JVM's ( SUN 1.3.1_15) permanent gen to fill up. Anyhow long story short 
this seems to be a known issue with this version of Rhino that has been 
fixed in 1.5R2.

I believe I can resolve the OOM issue by switching Rhino to run in 
interpreted mode . My question is can  Rhino *always* be switched to 
interpreted mode without breaking any application functionality? Or are 
there Rhino API's and coding patterns that will break the application 
when Rhino is switched from the default compiled mode to interpreted 
mode ? I.e can rhino transparently ,to the application,  be switch from 
compiled to interpreted mode or are there cases where the application 
has to be modified?


While I have your attention can anyone tell me if Rhino 1.5R2 is 
backwards compatible with 1.5R1 ?


Regards
-- Gordon

.