LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

The distribute object tools often crashes LabVIEW 2017

Solved!
Go to solution

Same problem here. LabVIEW 2017 32-bit on Windows 10 64-bit.

 

LabVIEW freezes very often when I use "Align Objects" or "Distribute Objects" (especially when wires are selected). There are only 140 VIs in my project. Only LVOOP classes come from dependencies (NI Modbus Library, JKI JSON).

 

The problem is killing me as I use align and distribute functions all the time. Right now, I seriously regret switching to LabVIEW 2017 from 2015 SP1.

Tomasz Czarnik, Fitech Sp. z o. o., Poland
0 Kudos
Message 11 of 18
(1,630 Views)

It's the same for me. LV2017 32bit on Win7 64bit.

It's time for Patch 1!

 

Greets, Dave
0 Kudos
Message 12 of 18
(1,625 Views)
Solution
Accepted by topic author Blokk

The issue has been reproduced and is being tracked under CAR #656295.

Dániel Fülöp
Field Application Engineer (CLA, CTA)
National Instruments
Message 13 of 18
(1,581 Views)
Solution
Accepted by topic author Blokk

Looks like that was a patch released that has this CAR fixed:

LabVIEW 2017 Patch Details

LabVIEW 2017 (32-bit) f2 Patch Download


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 14 of 18
(1,343 Views)

I already had this patch for a while, and I did not experience recently such crashes 🙂

0 Kudos
Message 15 of 18
(1,333 Views)

Hello everybody

 

I have been facing the same problem recently. If the VI was not auto-saved or manually saved, the chances of crashing were high.

 

I had contacted local NI couple of times about this and I was just asked to reinstall LabVIEW. This was in November.

 

If a CAR had been raised and solved in October, I am not sure why local NI support did not refer me to this link. I have been meaning to search the forums about this problem and just managed to do it. I had to reinstall twice on one PC. Now I began to see this problem on another system too and ended up at this link.

 

Regards
Freelance_LV
TestAutomation Consultant
0 Kudos
Message 16 of 18
(1,274 Views)

Installing LabVIEW 2017 f2 patch solved this problem for me.
http://www.ni.com/download/labview-development-system-2017/6967/en/

 

Regards,

Tomasz Czarnik, Fitech Sp. z o. o., Poland
0 Kudos
Message 17 of 18
(1,267 Views)

Just for good measure, this fix was included in the 2017 patch mentioned below and it's been included in the 2017 SP1 release.

 


@crossrulz wrote:

Looks like that was a patch released that has this CAR fixed:

LabVIEW 2017 Patch Details

LabVIEW 2017 (32-bit) f2 Patch Download


 

0 Kudos
Message 18 of 18
(1,229 Views)