Labview freezes while loading a subvi in edit mode

[tBlum]

Hi,

Since a while, labview on my computer freezes when i'm editing a vi and double-clicking on a subvi icon to load its front panel. This happens sporadically, then if i compulsively click on the subvi window, it will say "not responding", and a few minutes later (about 5min usually), the front panel is finally loaded and all my labview windows that were freezed are ok again. I tried to search similar threads but no success.
cheers,

thomas

[Jarrod_S.]

Which version of LV are you using? Do you have source code control configured? If so, LV will occassionally check the status of the VI in source code control when loading its front panel. If the source code control server is bogged down handling other requests, this could impact opening your VI, because LV will wait for the server to respond.

Message Edited by Jarrod S. on 05-22-2007 02:22 PM

[tBlum]

I' sorry i forgot to tell so i'm using labview 7.1.1 on a winxp PC, with a celeron 2.5GHz and 768MB RAM.
I don't know what source code control is, so the settings are propably the default ones, but I'll have a look at it.

Thomas

[Jarrod_S.]

Hmmm... If you haven't configured Source Code Control then the default options should be for it to be turned off.

You can check by going to the Tools menu and selecting Tools >> Source Code Control >> Configure SCC Options. If you see <Select a Provider> in the dropdown box, you don't have SCC configured. That is the default option.

(FYI: Source Code Control (SCC) is a way of sharing one set of files between multiple developers. All developers use copies of the same files stored on a central server. If you want to modify a file, you check it out, and no one else can modify it while you have it checked out. That helps you avoid conflicting changes. It also has version control which allows you to roll back changes you have made to a specific file or set of files.)

[MRedRaider]

Have you run a mass compile? If you have, did you get any errors or see any improvement?

(Can't remember in 7.1 but in 8.2 you click Tools>>Advanced>>Mass Compile and select your directory. You might want to mass compile the entire LabVIEW directory in C:\Program Files\National Instruments )

[MRedRaider]

Have you run a mass compile? If you have, did you get any errors or see any improvement?

(Can't remember in 7.1 but in 8.2 you click Tools>>Advanced>>Mass Compile and select your directory. You might want to mass compile the entire LabVIEW directory in C:\Program Files\National Instruments or your OS's equivalent)

Message Edited by MattH on 05-22-2007 02:56 PM

[tBlum]

Well I did run a mass compile after updating from 7.1 to 7.1.1, but didn't see any improvements. I had a few warnings, but i don't remember what they were, but no errors as far as a I remember.

Thomas

[MRedRaider]

Do you see this on any other computer?

(According to NI's licensing found: http://www.ni.com/license/licensing_options.htm you can install LabVIEW on up to 3 PCs and a home computer)

This would eliminate the PC itself and let us know if the problem is with a corrupted VI or with your LabVIEW installation...

If it works fine everywhere else, it may be time to do a full reinstall.

If it doesn't, you might try re-writing the subVI(s) that give you trouble.

[tBlum]

I don't remember seeing  it happening on an other computer, but my computer was entirely reinstalled about a month and a half ago. First I saw it on one subvi only but now it happens even on old subvi someone else made a long time ago. And I'd like to avoid a full reinstall as it might take a full day (i have NI-scope and many other add-ons on my pc)

Thomas

[Coal_Man]

Have you done a repair on your installation of LabVIEW?  It may correct the issue and would avoid having to do a complete reinstall of everything.