[jbosstools-issues] [JBoss JIRA] (JBIDE-26794) OpenShift: Remote debugging is very slow
André Dietisheim (Jira)
issues at jboss.org
Mon Aug 26 13:50:00 EDT 2019
[ https://issues.jboss.org/browse/JBIDE-26794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775455#comment-13775455 ]
André Dietisheim commented on JBIDE-26794:
------------------------------------------
I tried IntelliJ and also VSCode. VSCode behaves pretty much on par to Eclipse speedwise. IntelliJ on the other hand is noticeably quicker. It is noticeable in all 3 how building the callstack is very slow. While Eclipse/VSCode feel singlethreaded and wont accept inputs nor any other operation while the stack is being displayed, IntelliJ seems to do it in a separate (background) thread, it stays responsive even while building the callstack.
I definitely think that this is a platform issue and needs to be improved in the Eclipse/VSCode platform. IntelliJ has a noticeable advantage here. On the other hand, remote debugging - I think - isn't the dominant usecase.
> OpenShift: Remote debugging is very slow
> ----------------------------------------
>
> Key: JBIDE-26794
> URL: https://issues.jboss.org/browse/JBIDE-26794
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Environment: Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> RHPDS
> Reporter: Josef Kopriva
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.13.x
>
>
> From Email on devtools-team from [~jgammonred612]:
> {code:java}
> Hi Folks:
> Using this version of Code Ready Studio
> Version: 12.11.0.GA
> Build id: GA-v20190329-0120-B4247
> Build date: 20190329-0120
> I recently ran an Openshift Starter Workshop lab and witnessed a clear
> issue with Code Ready Studio and INtelliJ
> Workshop Starter Lab
> (http://starter-guides-labs.b9ad.pro-us-east-1.openshiftapps.com/workshop/workshop/lab/common-environment)
> Lab 19 has a remote debugging setup. The remote debugger in Code Ready
> connected very very slowly and would not step over or step out making
> using it as a debugger virtually impossible.
> One of the lab participants had IntelliJ and it connected immediately
> and worked just fine.
> Clearly, something is broken in CRS. Maybe someone would want to test
> this out and fix?
> You can find this lab on RHPDS.
> Just FYI to the PM's.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jbosstools-issues
mailing list