[
https://issues.jboss.org/browse/JBDS-4789?page=com.atlassian.jira.plugin....
]
Ondrej Dockal commented on JBDS-4789:
-------------------------------------
Issue was that property itself is called:
{code}org.eclipse.jdt.debug.PREF_SHOW_STEP_RESULT{code} and when in use in
plugin_customization.ini file, it must be preceded with plugin name
(_org.eclipse.jdt.debug_ and diviede by slash), so the final entrance in ini file is:
{code}org.eclipse.jdt.debug/org.eclipse.jdt.debug.PREF_SHOW_STEP_RESULT=false{code}
[~sbouchet-1] Thanks for finding this.
Disable "show method result after a step operation" by
default
--------------------------------------------------------------
Key: JBDS-4789
URL:
https://issues.jboss.org/browse/JBDS-4789
Project: Red Hat CodeReady Studio (devstudio)
Issue Type: Enhancement
Components: openshift, product
Affects Versions: 12.13.0.AM1
Reporter: André Dietisheim
Assignee: Ondrej Dockal
Priority: Major
Fix For: 12.13.0.AM1
Attachments: show-method-result-after-step-operation.png
Stepping over code while debugging is very very slow in current Eclipse. Turns out that
this is due to a preference setting that is enabled by default:
*show method result after a step operation*
!show-method-result-after-step-operation.png!
We thus should consider turning this off by default in CRStudio.
The issue is being reported/discussed in Eclipse bugs at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702 and
https://bugs.eclipse.org/bugs/show_bug.cgi?id=536751 where a slowdown of 10x is reported.
Eclipse thus is considering turning it off by default:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=533702#c7
This is especially painful when remote debugging applications in OpenShift: JBIDE-26794
--
This message was sent by Atlassian Jira
(v7.13.8#713008)