Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <20225364.1201298314627.JavaMail.jira@brutus>
Date: Fri, 25 Jan 2008 13:58:34 -0800 (PST)
From: "Gregory Shimansky (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-5145) [drlvm][gc] intermittent NPE in
 annotation tests
In-Reply-To: <11188050.1195452763002.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562705#action_12562705 ] 

Gregory Shimansky commented on HARMONY-5145:
--------------------------------------------

I believe this is a coincidence, but the same set of tests fail for me with a patch for JET that enables lazy resolution in -Dtest.mode=jet. The patch is located here https://issues.apache.org/jira/secure/attachment/12374089/lazy.patch 

The patch is most likely not yet correct, so HW NPE may be happening because of a bug. But it is interesting that it causes the same tests to fail and failure is reproducible in 100% of runs. Maybe fixing this NPE may give a pointer why the intermittent bug happens.

> [drlvm][gc] intermittent NPE in annotation tests
> ------------------------------------------------
>
>                 Key: HARMONY-5145
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5145
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Windows, Linux (x86_64 only ?)
>            Reporter: Alexey Varlamov
>            Assignee: Xiao-Feng Li
>
> Kernel tests fail intermittently with NPE, the top of stacktrace is always the same:
> java.lang.NullPointerException   
>  at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:200)   
>  at org.apache.harmony.lang.annotation.AnnotationFactory.createAnnotation(AnnotationFactory.java:101)   
> Brief review of j.l.reflect.Proxy code shows that possible reason of failure are nullified WeakReferences to proxy classes in interfaceCache. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.