Skip to main content
Question

Data Inspector via Windows Remote Desktop

M
Forum|alt.badge.img+2

Anyone using FME via a Windows Remote Desktop? Whenever using Data Inspector on my office based PC and I select a polygon feature inside the Remote Desktop session, my local machine Remote Desktop process starts to consume around 16% CPU and makes it unresponsive. Clearing the selection returns the CPU to 0%, as does minimising the Data Inspector.

This only happens when you select a feature, and the geometry is more than a simple geometric shape (rectangle, triangle, circle etc.), but doesn't have to be super complicated. Thought it was transparency related at first but it doesn't appear to be as get the same effect with solid colours.

Clearly could be an issue with the graphics driver on either PC but wondering if anyone else sees the same?

Sample data attached.

Remote Desktop running locally on Windows 10 (but saw same issue with Windows 7)

Data Inspector running remotely on Windows 7

FME 2017 (but see the same on earlier versions)

8 replies

ebygomm
Influencer
Forum|alt.badge.img+39
  • ebygommInfluencer
  • Influencer
  • August 17, 2017

I use FME via windows remote desktop every Monday and Friday and have never noticed any issues.

redgeographics
Celebrity
Forum|alt.badge.img+50

No experience with it myself, but some anecdotical evidence from clients using Direct Access to connect and reporting similar issues. In their case it seemed to be mostly Workbench (displaying the Quick Add transformers list). How is that behaving when you use it remotely?

david_r
Celebrity
  • david_rCelebrity
  • August 17, 2017

I use FME on Remote Desktop connections all the time but I've never had it go unresponsive on me the way you describe it.

However, I can confirm that something weird is going on when selecting the sample feature in the Data Inspector, my CPU usage jumps from about 0-1% to 30-ish% and stays there as long as the feature is selected. When I deselect the feature, the CPU usage goes back to 0-1% again, it's reproducible.

This happens both on my local pc (FME 2017.1) and on the remote desktop instance (FME 2016.1.2) that I tested.

After having looked into it, I think I've isolated the issue, which in fact looks like it's linked to whether the collapsed list of vertices is visible in the feature information window:

If you either add some attributes or make the Inspector window smaller so that the collapsed vertices aren't visible on screen, the CPU usage drops down to about zero. If I click on "Show All" the CPU usage also drops again. This was 100% reproducible on my PC.

Something funky is going on in the source code of that widget, Safe should definitely take a closer look.

M
Forum|alt.badge.img+2
  • mark_f
  • Author
  • August 17, 2017
redgeographics wrote:

No experience with it myself, but some anecdotical evidence from clients using Direct Access to connect and reporting similar issues. In their case it seemed to be mostly Workbench (displaying the Quick Add transformers list). How is that behaving when you use it remotely?

No problems with Workbench remotely whatsoever.

 

 

M
Forum|alt.badge.img+2
  • mark_f
  • Author
  • August 17, 2017
david_r wrote:

I use FME on Remote Desktop connections all the time but I've never had it go unresponsive on me the way you describe it.

However, I can confirm that something weird is going on when selecting the sample feature in the Data Inspector, my CPU usage jumps from about 0-1% to 30-ish% and stays there as long as the feature is selected. When I deselect the feature, the CPU usage goes back to 0-1% again, it's reproducible.

This happens both on my local pc (FME 2017.1) and on the remote desktop instance (FME 2016.1.2) that I tested.

After having looked into it, I think I've isolated the issue, which in fact looks like it's linked to whether the collapsed list of vertices is visible in the feature information window:

If you either add some attributes or make the Inspector window smaller so that the collapsed vertices aren't visible on screen, the CPU usage drops down to about zero. If I click on "Show All" the CPU usage also drops again. This was 100% reproducible on my PC.

Something funky is going on in the source code of that widget, Safe should definitely take a closer look.

Good detective work! I just assumed was because I was remote it was that, but as you say get the same issue locally.

 

 

Collapsing the entire coordinate node also works to reduce the CPU back to normal levels.

 

 

david_r
Celebrity
  • david_rCelebrity
  • August 17, 2017
mark_f wrote:
Good detective work! I just assumed was because I was remote it was that, but as you say get the same issue locally.

 

 

Collapsing the entire coordinate node also works to reduce the CPU back to normal levels.

 

 

Yes, it seems that it's the "on-screen presence" of that particular widget that's the issue.
M
Forum|alt.badge.img+2
  • mark_f
  • Author
  • August 17, 2017
ebygomm wrote:

I use FME via windows remote desktop every Monday and Friday and have never noticed any issues.

Normally OK for me as well, but have seen this before and today it really bugged me enough to ask!

 

As @david_r found not just related to remote desktop, but local processes. I guess when affects the Remote Desktop process maybe it is more obvious.

 

M
Forum|alt.badge.img+2
  • mark_f
  • Author
  • August 17, 2017
david_r wrote:
Yes, it seems that it's the "on-screen presence" of that particular widget that's the issue.

 

Logged with Safe Support - will post back any updates

Reply


Helpful Members This Week

Community Stats

31,423
Posts
119,155
Replies
39,047
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.