Vision performance issues with "File Explorer" component

Ignition
1

Hi everyone,

I’m experiencing performance issues with the "File Explorer" component in Vision. Whenever a client accesses the page with this component, the system slows down significantly and remains unresponsive for a few minutes until the page finishes loading.

Once the page has fully loaded, users can interact with the component without any further issues. The problem seems to be isolated to the initial loading phase, even for a single user accessing the page.

For context, I’m using the following script to clear the "selected path" of the component upon page load:

system.gui.getParentWindow(event).getComponentForPath('Root Container.File Explorer').selectedPath = ' '

Any suggestions to resolve this problem?
Thanks everyone

2

Have you tried not setting the selected path? (It has to search all your drives for folders if you set that to empty.)

3

I tried not to set the selected path by disabling the script opening the page but nothing changes.

I am sure that the problem is the "File Explorer" component because I have done various tests and finally leaving only it in the page without any script or binding still gives the problem of strong slowdown in entering the page.

The version of Ignition that I am using is: 8.1.42

4

Is this a new application? Or is this something that slowed down post-upgrade?

(I never use this component, so I don't know if it was ever fast.)

5

This is the first time I use this component too.
The application is not new, I upgraded Ignition to version 8.1.42 months ago and never had any issues like this.

I was just developing a new page where I needed to use the "File Explorer" and I noticed this slowdown problem.

So I turned here on the forum to see if anyone else has the same problem.

6

I normally set the ROOT PATH to a folder on the C drive with barely anything in it. If not it loads everything from the windows system, one drive, network drives, etc.

Then for the selected path set it to None instead of ' '

2 Likes
7

I think both things are true.

  1. The component is erroneously doing the tree node construction eagerly and on the main GUI thread. That's a bug.
  2. The way you are using the file explorer is inviting this bug. I think @MMaynard's suggestion is appropriate as a workaround.

We absolutely should still fix this, but that's not going to happen any time soon, so if you want to use this component, you're going to want a workaround.

1 Like
8

Ok. I'll follow @MMaynard's advice to work around this until this bug is fixed then.
Thanks everyone!