LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV2013 hangs on Resolve Load Conflict Dialog

I am also curious, are you are using source code control? specifically tortoise SVN?

 

Thanks,

 

Jeff

0 Kudos
Message 11 of 39
(1,026 Views)

Yes, I'm using tortoise SVN and have the VSI TSVN tools installed also.

0 Kudos
Message 12 of 39
(1,017 Views)

Did you try to reproduce it in a VI which is included in a project? I forgot to mention that I had created a project also.

0 Kudos
Message 13 of 39
(1,011 Views)

I am also using TortoiseSVN and the VSI TSVN Toolkit.

0 Kudos
Message 14 of 39
(1,009 Views)

Hi,

 

today this happened to me.

I tried to do a "Save as..." from project explorer. LabVIEW showed a loading dialog (...\resource\Framework\Providers\API\mxlvgetfilepathbatch.vi) and didn't return.

 

I have LabVIEW2013 (13.0f2), TSVN 1.8.4 and VSI TSVN Toolkit 1.8.0.0.

 

I saw this happen in other circumstances, but can't remember what I did back then.

 

UliB

0 Kudos
Message 15 of 39
(981 Views)

Hello,

 

Can you try doing a mass compile of the VSI TSN Toolkit directory? I would also be interested in seeing if a reinstall of that toolkit causes this to go away.

 

Thanks,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

Message 16 of 39
(975 Views)

Hello Jeff,

 

I did a mass compile of the VSI TSVN Toolkit directory. There are two Bad VIs (see attachment "20131216_VSI TSVN Toolbar.txt").

 

After that I tired a "Save As ..." from project explorer. The "Save As" dialog appears. After a few seconds a loading dialog for "mxLvGetFilePathBatch.vi" appears. Luckily the "Save As .." dialog stays in front and can be accepted or canceled.

This loading dialog came up twice out of six tries. So I don't know if this can be called reproducible. But LV did not hang.

 

Then I uninstalled and reinstalled the toolkit. The behavior did not change. The dialog appears in two out of many tries.

 

UliB

0 Kudos
Message 17 of 39
(946 Views)

I may have an easier method to reproduce.

 

Launch a dialog vi via ACBR Fire and forget.

Forget to drop an Open FP method on your dialog.  (Of course this means that you have some silly dialog running without its FP Open which is not really what you want to doSmiley Embarassed)

 

Try to open the dialog from the project you will get this little reminder that you did something silly

Capture.PNG

 

20 minutes later I have 294 vis loaded.  slowly


"Should be" isn't "Is" -Jay
0 Kudos
Message 18 of 39
(930 Views)

Mass Compile on <Resource>Framework\Providers\API seems to solve the issue.

 

Thanks for the tip Mr. Peacock


"Should be" isn't "Is" -Jay
0 Kudos
Message 19 of 39
(913 Views)

Just as an update - we have been working with Viewpoint and think we may have determined the root cause of this. We will continue to update this thread as we get more information.

 

Thanks,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

Message 20 of 39
(892 Views)