[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Warnings from the bindings

From: Branko ─îibej <brane_at_apache.org>
Date: Tue, 3 Apr 2018 14:32:45 +0200

On 03.04.2018 13:28, Stefan Fuhrmann wrote:
> On 30.03.2018 00:27, Philip Martin wrote:
>

>> WARNING in native method: JNI call made without checking exceptions when required to from CallStaticObjectMethod
> Seen these in alpha2 but not in rc2. Java8 has
> been updated since then.

I don't see this on OSX with 1.8.0_45-b14.

>> but it's not clear to me which bit of source code is responsible. There
>> are also warnings for:
>>
>> WARNING: JNI local refs: 33, exceeds capacity: 32
>> at org.apache.subversion.javahl.util.PropLib.unparseExternals(Native Method)
>> at org.apache.subversion.javahl.SVNUtil.unparseExternals(SVNUtil.java:790)
> Those are a known issue. There used to be 10-ish
> such warnings and now they are down to 3. I vaguely
> recall that there had been an actual fix and we are
> now seeing the remaining unpatched occurrences.

And I don't see these, either. I checked the code and we explicitly use
a JNI local frame in the core loop of unparseExternals. Try as I might,
I can't see where all those local references could be coming from.

-- Brane
Received on 2018-04-03 14:32:50 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.