serviceability-dev  

Messages by Thread

• • Integrated: 8350441: ZGC: Overhaul Page Allocation Joel Sikström
• RFR: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK Jiangli Zhou
  • Re: RFR: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK Jiangli Zhou
  • Re: RFR: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK [v2] Jiangli Zhou
  • Re: RFR: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK [v2] Jiangli Zhou
  • Re: RFR: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK [v2] Alan Bateman
  • Re: RFR: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK [v2] Jiangli Zhou
  • Re: RFR: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK [v3] Jiangli Zhou
  • Re: RFR: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK [v3] Alan Bateman
  • Integrated: 8353938: hotspot/jtreg/serviceability/dcmd/jvmti/LoadAgentDcmdTest.java fails on static JDK Jiangli Zhou
• RFR: 8353485: Jcms should allow to specify streaming_output mode Alex Menkov
  • Withdrawn: 8353485: Jcms should allow to specify streaming_output mode Alex Menkov
  • Re: RFR: 8353485: Jcms should allow to specify streaming_output mode Alex Menkov
• RFR: 8353727: HeapDumpPath doesn't expand %p Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p Zhengyu Gu
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p Chris Plummer
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Thomas Stuefe
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Thomas Stuefe
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Thomas Stuefe
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Leonid Mesnik
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Thomas Stuefe
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v2] Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v3] Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v3] Thomas Stuefe
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v4] Kevin Walls
  • Re: RFR: 8353727: HeapDumpPath doesn't expand %p [v4] Kevin Walls
  • Integrated: 8353727: HeapDumpPath doesn't expand %p Kevin Walls
• RFR: 8353597: Refactor handling VM options for AOT cache input and output Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v2] Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v2] Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v2] Vladimir Kozlov
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v2] Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v2] Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v2] Leonid Mesnik
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v2] Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v3] Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v3] Dan Heidinga
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v3] Vladimir Kozlov
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v3] Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v3] Dan Heidinga
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v3] Vladimir Kozlov
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v4] Ioi Lam
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v4] Ashutosh Mehra
  • Re: RFR: 8353597: Refactor handling VM options for AOT cache input and output [v4] Vladimir Kozlov
  • Integrated: 8353597: Refactor handling VM options for AOT cache input and output Ioi Lam
• RFR: 8352652: [BACKOUT] nsk/jvmti/ tests should fail when nsk_jvmti_setFailStatus() is called David Holmes
  • Re: RFR: 8352652: [BACKOUT] nsk/jvmti/ tests should fail when nsk_jvmti_setFailStatus() is called Leonid Mesnik
  • Re: RFR: 8352652: [BACKOUT] nsk/jvmti/ tests should fail when nsk_jvmti_setFailStatus() is called David Holmes
  • Integrated: 8352652: [BACKOUT] nsk/jvmti/ tests should fail when nsk_jvmti_setFailStatus() is called David Holmes
• RFR: 8351310: Deprecate com.sun.jdi.JDIPermission for removal Kevin Walls
  • Re: RFR: 8351310: Deprecate com.sun.jdi.JDIPermission for removal Serguei Spitsyn
  • Re: RFR: 8351310: Deprecate com.sun.jdi.JDIPermission for removal Chris Plummer
  • Re: RFR: 8351310: Deprecate com.sun.jdi.JDIPermission for removal Kevin Walls
  • Integrated: 8351310: Deprecate com.sun.jdi.JDIPermission for removal Kevin Walls
• RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v2] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v2] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v2] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v3] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v4] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v4] Leonid Mesnik
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v4] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v4] Patricio Chilano Mateo
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v4] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v5] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v6] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v6] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v6] Patricio Chilano Mateo
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v6] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v6] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v6] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v6] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v6] Patricio Chilano Mateo
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v7] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v8] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v8] Patricio Chilano Mateo
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v8] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v9] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v9] Patricio Chilano Mateo
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v9] Serguei Spitsyn
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v9] Leonid Mesnik
  • Re: RFR: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out [v9] Serguei Spitsyn
  • Integrated: 8316682: serviceability/jvmti/vthread/SelfSuspendDisablerTest timed out Serguei Spitsyn
• Withdrawn: 8336017: Deprecate java.util.logging.LoggingMXBean, its implementation, and accessor method for removal duke
• RFR: 8353479: jcmd with streaming output breaks intendation Alex Menkov
  • Re: RFR: 8353479: jcmd with streaming output breaks intendation Alex Menkov
  • Re: RFR: 8353479: jcmd with streaming output breaks intendation Serguei Spitsyn
  • Re: RFR: 8353479: jcmd with streaming output breaks intendation Johan Sjölen
• RFR: 8353231: Test com/sun/management/OperatingSystemMXBean/GetProcessCpuLoad still fails intermittently Kevin Walls
  • Re: RFR: 8353231: Test com/sun/management/OperatingSystemMXBean/GetProcessCpuLoad still fails intermittently David Holmes
  • Integrated: 8353231: Test com/sun/management/OperatingSystemMXBean/GetProcessCpuLoad still fails intermittently Kevin Walls
  • Re: RFR: 8353231: Test com/sun/management/OperatingSystemMXBean/GetProcessCpuLoad still fails intermittently Kevin Walls
• Debugger overhead for virtual threads creation Egor Ushakov
  • Re: Debugger overhead for virtual threads creation Chris Plummer
  • Re: Debugger overhead for virtual threads creation Egor Ushakov
  • Re: Debugger overhead for virtual threads creation Serguei Spitsyn
  • Re: Debugger overhead for virtual threads creation Chris Plummer
• Re: RFR: 8336881: [Linux] Support for hierarchical limits for Metrics [v17] Severin Gehwolf
  • Re: RFR: 8336881: [Linux] Support for hierarchical limits for Metrics [v17] Severin Gehwolf
  • Re: RFR: 8336881: [Linux] Support for hierarchical limits for Metrics [v17] Severin Gehwolf
• RFR: 8323100: com/sun/tools/attach/StartManagementAgent.java failed with "WaitForSingleObject failed" David Holmes
  • Re: RFR: 8323100: com/sun/tools/attach/StartManagementAgent.java failed with "WaitForSingleObject failed" Alex Menkov
  • Re: RFR: 8323100: com/sun/tools/attach/StartManagementAgent.java failed with "WaitForSingleObject failed" David Holmes
  • Integrated: 8323100: com/sun/tools/attach/StartManagementAgent.java failed with "WaitForSingleObject failed" David Holmes
  • Re: RFR: 8323100: com/sun/tools/attach/StartManagementAgent.java failed with "WaitForSingleObject failed" Kevin Walls
  • Re: RFR: 8323100: com/sun/tools/attach/StartManagementAgent.java failed with "WaitForSingleObject failed" David Holmes
• RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 Larry Cable
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 Jaikiran Pai
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 David Holmes
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v3] David Holmes
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 Jaikiran Pai
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v2] Larry Cable
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v3] Jaikiran Pai
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 Jaikiran Pai
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v2] Larry Cable
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v3] Larry Cable
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v3] David Holmes
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v3] Larry Cable
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v3] David Holmes
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v3] Serguei Spitsyn
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v3] Larry Cable
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v4] Larry Cable
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v4] David Holmes
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v5] Larry Cable
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v5] David Holmes
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v5] Kevin Walls
  • Re: RFR: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 [v5] Sergey Bylokhov
  • Integrated: 8344671: Few JFR streaming tests fail with application not alive error on MacOS 15 Larry Cable
• RFR: 8352773: JVMTI should disable events during java upcalls Chris Plummer
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM Jaikiran Pai
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM Jaikiran Pai
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v2] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v3] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v4] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v4] Jaikiran Pai
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v4] Alan Bateman
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v4] Coleen Phillimore
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v4] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v4] Serguei Spitsyn
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v4] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v2] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v2] Alan Bateman
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v2] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v2] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v2] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v2] Alan Bateman
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v6] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v6] Serguei Spitsyn
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v6] Jaikiran Pai
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v6] Alan Bateman
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v6] Chris Plummer
  • Integrated: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v7] Chris Plummer
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v7] Serguei Spitsyn
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v7] Jaikiran Pai
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v7] Alan Bateman
  • Re: RFR: 8352088: Call of com.sun.jdi.ThreadReference.threadGroups() can lock up target VM [v7] Chris Plummer
  • RFR: 8352773: JVMTI should disable events during java upcalls Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Alan Bateman
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Coleen Phillimore
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v2] Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Leonid Mesnik
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Chris Plummer
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v2] Chris Plummer
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v3] Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Chris Plummer
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v2] Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v3] Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v3] David Holmes
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v3] Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v3] Leonid Mesnik
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v3] Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v4] Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v4] Leonid Mesnik
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v4] Chris Plummer
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v4] David Holmes
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls [v4] Serguei Spitsyn
  • Re: RFR: 8352773: JVMTI should disable events during java upcalls Serguei Spitsyn
  • Integrated: 8352773: JVMTI should disable events during java upcalls Serguei Spitsyn
• RFR: 8352730: RISC-V: Disable tests in qemu-user Robbin Ehn
  • Re: RFR: 8352730: RISC-V: Disable tests in qemu-user Fei Yang
  • Re: RFR: 8352730: RISC-V: Disable tests in qemu-user Robbin Ehn
  • Re: RFR: 8352730: RISC-V: Disable tests in qemu-user Alan Bateman
  • Re: RFR: 8352730: RISC-V: Disable tests in qemu-user Robbin Ehn
  • Re: RFR: 8352730: RISC-V: Disable tests in qemu-user [v2] Robbin Ehn
  • Re: RFR: 8352730: RISC-V: Disable tests in qemu-user [v2] Hamlin Li

• Earlier messages
• Later messages