There is one more problem with running several DRLVM instances with GCv5 on a weak machine, which is currently used for CruiseControl runs. This breaks jdk_tools CC results. I've found existing HARMONY-3756 and provided details there.
Thanks. Ivan On 5/8/07, Ivan Popov <[EMAIL PROTECTED]> wrote:
There is another problem with running JPDA unit tests on Linux SLES10. I submitted https://issues.apache.org/jira/browse/HARMONY-3822 Thanks. Ivan On 5/7/07, Xiao-Feng Li <[EMAIL PROTECTED]> wrote: > Thanks. Will check. -xiaofeng > > On 5/7/07, Ivan Popov <[EMAIL PROTECTED]> wrote: > > I submitted https://issues.apache.org/jira/browse/HARMONY-3820 > > > > Thanks. > > Ivan > > > > On 5/7/07, Ivan Popov <[EMAIL PROTECTED]> wrote: > > > I see many Eclipse TPTP profiler tests failed today after switching > > > Harmony to GCv5. This failure needs deeper investigation, but at the > > > first glance it was caused by incorrect reporting JVMTI threads. Also, > > > I see strange threads list in Eclipse debugger. The "main" thread > > > group now contains lot of "finalizer" threads and does not include > > > "main" thread. Using gc_cc.dll solves this problem. I'm going to > > > submit JIRA against GCv5. > > > > > > Thanks. > > > Ivan > > > > > > PS: > > > Threads reported by Eclipse debugger (using gc_gen): > > > > > > HelloWorld at localhost:1067 > > > Thread Group [system] > > > Thread Group [main] > > > Daemon Thread [ref handler] (Running) > > > Daemon Thread [finalizer] (Running) > > > Daemon Thread [finalizer] (Running) > > > Daemon Thread [finalizer] (Running) > > > Daemon Thread [finalizer] (Running) > > > Daemon Thread [finalizer] (Running) > > > Daemon Thread [finalizer] (Running) > > > Daemon Thread [finalizer] (Running) > > > Daemon Thread [finalizer] (Running) > > > > > > Threads reported by Eclipse debugger (using gc_cc.dll) > > > > > > HelloWorld at localhost:1045 > > > Thread Group [system] > > > Daemon System Thread [FinalizerThread] (Running) > > > Thread Group [main] > > > Thread [main] (Suspended (breakpoint at line 5 in HelloWorld)) > > > HelloWorld.main(String[]) line: 5 > > > > > > > > > On 5/6/07, Xiao-Feng Li <[EMAIL PROTECTED]> wrote: > > > > Hi, folks, I've switched GCv5 to be the default GC. In today's > > > > CruiseControl tests with GCv5, shown at > > > > http://www.harmonytest.org/upload/cc2.html, we can see all tests > > > > passed. I known there are still potential bugs, we fix them once > > > > exposed. > > > > > > > > If you have some workloads having problem with GCv5, please try GCv4.1 > > > > with command option -XX:vm.dlls=gc_cc.dll . At the moment, there are > > > > two known issues, one is the intermittent failure with kernel.test > > > > java.langThreadTest; the other is that it has currently minimum 256MB > > > > heap size. The former one is hard to reproduce, the second one is easy > > > > to fix. Welcome feedbacks and suggestions. Thanks. > > > > > > > > There are still lots of work to do to make Harmony GC close to be > > > > perfect. To switch from GCv4.1 to GCv5 is only one step towards the > > > > goal, well it is an important step in my opinion. Next step, besides > > > > continuing GCv5 polishment, is to develop a low-pause-time GC. I will > > > > post a high level design soon. > > > > > > > > Thanks, > > > > xiaofeng > > > > > > > > > > > > -- > http://xiao-feng.blogspot.com >
