You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Pavel Rebriy (JIRA)" <ji...@apache.org> on 2008/03/17 11:07:24 UTC
[jira] Commented: (HARMONY-5172) [drlvm][thread] Failed assertion
on realibility test in lock unreservation code
[ https://issues.apache.org/jira/browse/HARMONY-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579373#action_12579373 ]
Pavel Rebriy commented on HARMONY-5172:
---------------------------------------
I've tried to reproduce the failure on AddRmPropertiesHooksTest reliability test with debug revision 635802.
Test passed 500 times (run duration is about 168 hours = a week).
I think the bug could be closed due to it is already fixed.
> [drlvm][thread] Failed assertion on realibility test in lock unreservation code
> -------------------------------------------------------------------------------
>
> Key: HARMONY-5172
> URL: https://issues.apache.org/jira/browse/HARMONY-5172
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Windows ia32
> Reporter: Gregory Shimansky
>
> When running reliability test AddRmPropertiesHooksTest on debug VM I sometimes hit the following assertion on thread_native_thin_monitor.cpp:144 - assert (IS_RESERVED(lockword)). Native stack trace looks like this:
> hythr.dll!_assert(const char * expr=0x1004ad58, const char * filename=0x1004ad00, unsigned int lineno=144) Line 295 C
> > hythr.dll!unreserve_self_lock(unsigned int * lockword_ptr=0x120b3c44) Line 144 + 0x1f bytes C
> hythr.dll!hythread_inflate_lock(unsigned int * lockword_ptr=0x120b3c44) Line 629 + 0x9 bytes C
> harmonyvm.dll!jthread_monitor_timed_wait(_jobject * monitor=0x0013f024, __int64 millis=0, int nanos=0) Line 313 + 0x9 bytes C++
> harmonyvm.dll!Java_java_lang_VMThreadManager_wait(JNIEnv_External * env=0x023a8080, _jobject * clazz=0x0013f020, _jobject * monitor=0x0013f024, __int64 millis=0, int nanos=0) Line 205 + 0x15 bytes C++
> 03353334()
> Java stack trace looks like this:
> The stack trace of the 01339930 java thread:
> [01339930] 00000000(n): java/lang/VMThreadManager.wait(Ljava/lang/Object;JI)I
> [01339930] 036D85D5(m): java/lang/Object.wait()V
> [01339930] 033A737C(m): java/lang/Thread.join()V
> org/apache/harmony/test/reliability/api/kernel/hooks/AddRmPropertiesHooksTest.waitForRunningThreads([Ljava/lang/Thread;)V
> [01339930] 033A63B8(m): org/apache/harmony/test/reliability/api/kernel/hooks/AddRmPropertiesHooksTest.addRemoveBeingRunningHooks()Z
> [01339930] 033A5663(m): org/apache/harmony/test/reliability/api/kernel/hooks/AddRmPropertiesHooksTest.playWithShutdownHooks()Z
> [01339930] 033A2AF8(m): org/apache/harmony/test/reliability/api/kernel/hooks/AddRmPropertiesHooksTest.test([Ljava/lang/String;)I
> [01339930] 033A10F7(m): org/apache/harmony/test/reliability/share/LongRunningTestStarter.test([Ljava/lang/String;)I
> [01339930] 033A06E6(m): org/apache/harmony/test/reliability/share/ReliabilityTestStarter.test([Ljava/lang/String;)I
> [01339930] 033A033F(m): org/apache/harmony/test/reliability/share/ReliabilityTestStarter.main([Ljava/lang/String;)V
> To run the test from command line I used the following command line in reliability test suite:
> $ ~/harmony/trunk/working_vm/build/win_ia32_msvc_debug/deploy/jdk/jre/bin/java -cp deploy/classes org.apache.harmony.test.reliability.share.ReliabilityTestStarter -testClassName org.apache.harmony.test.reliability.api.kernel.hooks.AddRmPropertiesHooksTest 1000 100
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.