LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV2013 hangs on Resolve Load Conflict Dialog

Hi,

 

I've noticed that LV2013 hangs on Resolve Load Conflict Dialog on certain situations. I noticed this recently with the CDL API but I have seen this before in other circumstances not related to that API.

I have newest versions of CVT v3 and CDL APIs installed along with other Current Value Table related APIs like STM, CIE, CCC.

 

One way to reproduce this is by creating a new VI and placing "CDL Start Data Logger.vi" to the block diagram and creating a constant to the Tag List input. After this place "CDL Example_Advanced.vi" to the same block diagram. The resolve load conflict dialog appears. Now, if you wait for a couple of seconds before choosing the correct VI to be loaded, you'll see a new loading/search window. It says it is trying to load "...\LabVIEW 2013\resource\Framework\Providers\API\mxLvGetFilePathBatch.vi" but it never completes. When you try to stop or close the window for a couple of times,  nothing happens or LabVIEW crashes. Most of the time I've had to end LabVIEW.exe from Task Manager.

 

If you quickly select the correct item from the list and press "Load with Selected" this doesn't happen.

 

Attached is a screenshot of the situation and crash report.

 

Has anyone else seen such behaviour?

 

-Matti

Download All
0 Kudos
Message 1 of 39
(4,318 Views)

Yes, I have seen this behavior in certain situations with 2013.  I have't had time to try to reproduce it yet.

 

Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome
0 Kudos
Message 2 of 39
(4,255 Views)

Yes, I've been having the same issue. I've seen it when trying to do a "Save As" from the Project Explorer. I also just had it happen today when trying to add a VI to the project. It appeared just after an Update Dependencies dialog. Extremely annoying...

0 Kudos
Message 3 of 39
(4,231 Views)
It alway happens while trying to load mxLvGetFilePathBatch.vi.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome
0 Kudos
Message 4 of 39
(4,225 Views)

Hi,

 

Ok, so it seems there's other people also having similar issues.

 

I just noticed that I can't reproduce this crash if the LabVIEW version is known for all the VIs in the "Conflicting Items" list. If there is "???"-marks in the version cell for some VI in the list the crash I described earlier is likely to happen.

 

Does anyone from NI have better information about this?

 

-Matti

0 Kudos
Message 5 of 39
(4,204 Views)

@Matti_Autioniemi wrote:

Hi,

 

Ok, so it seems there's other people also having similar issues.

 

I just noticed that I can't reproduce this crash if the LabVIEW version is known for all the VIs in the "Conflicting Items" list. If there is "???"-marks in the version cell for some VI in the list the crash I described earlier is likely to happen.

 

Does anyone from NI have better information about this?

 

-Matti


Hi Matti,

 

Are you getting a crash or a hang? If you are getting a crash, did you hit the 'Send Report' button on the crash dialog? If you did, do you have the Report ID (long alphanumeric number)? I can look it up to see if there is any information about the root cause. Has anyone seen this behavior in a version other than 2013? Are you able to reproduce it on multiple computers with the same project or is it specific to a single system?

 

Thanks,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

 

edit - just saw that you are getting a hang and sometimes get a crash after. Please let me know if you have a report ID that I can look up.

0 Kudos
Message 6 of 39
(4,188 Views)

If you did send in the crash reports already but don't have the IDs, you can find the reports in Documents\LabVIEW Data\LVInternalReports\LabVIEW\13.0f2 (32-bit)\ or the corresponding version. The folder names are the report IDs.

 

Thanks,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

0 Kudos
Message 7 of 39
(4,179 Views)

Jeff - mine from yesterday was 6557c025-0e3f-462b-b591-3d3c4d8f2b97.

 

I don't recall if I sent it in, so I attached the zip file here as well. 

 

-Andrew

0 Kudos
Message 8 of 39
(4,175 Views)

Hi,

 

Yes, I have the report ID and I sent the report also.

 

Here it is: 0eea04e3-74d3-4276-8b7e-0aca027c15ed

You can also find it from the attachments in my first post.

 

Yes, I have been able reproduce it on multiple computers and on different projects.

 

-Matti

 

 

0 Kudos
Message 9 of 39
(4,167 Views)

@Matti_Autioniemi wrote:

Hi,

 

I've noticed that LV2013 hangs on Resolve Load Conflict Dialog on certain situations. I noticed this recently with the CDL API but I have seen this before in other circumstances not related to that API.

I have newest versions of CVT v3 and CDL APIs installed along with other Current Value Table related APIs like STM, CIE, CCC.

 

One way to reproduce this is by creating a new VI and placing "CDL Start Data Logger.vi" to the block diagram and creating a constant to the Tag List input. After this place "CDL Example_Advanced.vi" to the same block diagram. The resolve load conflict dialog appears. Now, if you wait for a couple of seconds before choosing the correct VI to be loaded, you'll see a new loading/search window. It says it is trying to load "...\LabVIEW 2013\resource\Framework\Providers\API\mxLvGetFilePathBatch.vi" but it never completes. When you try to stop or close the window for a couple of times,  nothing happens or LabVIEW crashes. Most of the time I've had to end LabVIEW.exe from Task Manager.

 

If you quickly select the correct item from the list and press "Load with Selected" this doesn't happen.

 

Attached is a screenshot of the situation and crash report.

 

Has anyone else seen such behaviour?

 

-Matti


I followed these steps exactly, and while I got load warnings about changing dependencies dropping both nodes, I did not get a resolve conflicts dialog. Is there anything different you are doing? My steps - 

1) Quick Drop CDL Start Data Logger (Load Warning pops up about new path)

2) Dismiss load warning

3) Create constant from the Tag List terminal

4) Quick Drop CDL Example Advanced (Load Warning pops up)

5) Dismiss load warning

6) no hang

 

Thanks for the report IDs,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

0 Kudos
Message 10 of 39
(4,159 Views)