This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : 201005312001 ] [ JDK VERSION : 1.6.20 ] Remote-Debugging is very slow
Created attachment 100053 [details] Profiler Snapshot
It looks like most of the time is spent in ThreadReference.frameCount() and ThreadReference.frame() that are called from various places and various threads. Perhaps this could be cached. Some time is also spent by disabling of breakpoints before method invocations and enabling them back afterwards. Do you have a lot of breakpoints submitted?
>Do you have a lot of breakpoints submitted? No. I set 5 breakpoints.
Fix of issue #187736 will improve the performance slightly, since we will not be disabling and enabling breakpoints around every method invocation.
Performance should be improved by changeset: 174914:dfccc159581f http://hg.netbeans.org/main/rev/dfccc159581f We cache stack depth, stack frames are cached in JDK 7, the caching that is implemented in JDK 6 is not much efficient. We also prevent from IncompatibleThreadStateException that could be internally thrown and slowed down the execution.
Integrated into 'main-golden', will be available in build *201007290001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/dfccc159581f User: mentlicher@netbeans.org Log: #187533, #188732 Cache the thread stack depth and assure that stack frames are retrieved only for suspended threads (thus preventing from IncompatibleThreadStateException. Also suspendedNoFire is set to false when a thread is resumed. This should also prevent from bug #141061.