[Sablevm-developer] Re: [Sablevm-bugs] [ sablevm-Bugs-663270 ] [jni: fatal error (Local reference capacity exceeded)]

[Etienne M. G. <eti...@uq...>]

First of all, I wish a happy new year 2003 to everyone.

This seems to be a local reference leak in Classpath...  The JNI
specification says that a VM automatically reserves at least 16 local
references.  To use additional references, the EnsureLocalCapacity()
JNI function is available and shoould be called.

See:
http://java.sun.com/products/jdk/1.2/docs/guide/jni/jni-12.html#EnsureLocalCapacity

A VM is *NOT* required to provide any more than 16 native references,
by default, and can halt abruptly by calling FatalError() if it cannot
create more locals. [OK, there's a note about backward compatibility,
but my understanding is that this is for the JDK, not for every
possible VM].

SableVM is simply strict in its implementation of the JNI spec (which
simplifies local reference management a little).

In fact, by aborting as it does, SableVM is helping to detect
weaknesses in the Classpath native library.

I personally think that this sould be filed as a bug against
Classpath, instead.

But, maybe I'll add a configure option to enable growing the local ref
frame automatically.  It shouldn't take more than 10 lines of code and
would make Archie happy;-)

Etienne

On Mon, Jan 06, 2003 at 11:16:53AM -0800, SourceForge.net wrote:
> Bugs item #663270, was opened at 2003-01-06 11:16
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=105523&aid=663270&group_id=5523
> 
> Category: Execution Problem
> Group: SableVM
> Status: Open
> Resolution: None
> Priority: 5
> Submitted By: Archie Cobbs (archiecobbs)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: [jni: fatal error (Local reference capacity exceeded)]
> 
> Initial Comment:
> I'm trying to run an application that uses Soot. If I
> try to process
> too many classfiles at once, I get this error plus a
> core dump:
> 
>   [jni: fatal error (Local reference capacity exceeded)]
> 
> This makes SableVM suddenly look like a "toy" Java VM when
> we know it's really better than that :-)
> 
> SableVM should handle this situation more gracefully,
> even if
> it means an 'escape' mechanism that's slower than normal or
> whatever.
> 
> 
> ----------------------------------------------------------------------
> 
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=105523&aid=663270&group_id=5523
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Sablevm-bugs mailing list
> Sab...@li...
> https://lists.sourceforge.net/lists/listinfo/sablevm-bugs

-- 
Etienne M. Gagnon                    http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/