LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Autoindexing a map crashes LV64

I'm using the new map functions in LV2019. They seem to work fine in the 32 bit version but crash the 64 bit version.

Map breaks 64_BD.png

CLED (2016)
0 Kudos
Message 1 of 4
(2,247 Views)

I opened and ran your vi in LabVIEW 2019 64-bit (19.0f1).  I didn't get any crashes.

Message 2 of 4
(2,099 Views)

Thanks for testing. I was running 2019. I checked the update service and didn't see anything so I didn't know about the f1. I upgraded and the crash went away!

Message 3 of 4
(2,073 Views)

Anyone else still get crashes?  When I'm using maps in 64 bit (the maps are actually private data w/in a class) the OS nukes the whole works in an unhandled crash.

LabVIEW 2024 Q4 64 bit.

 

 

Faulting application name: FATS.exe, version: 0.0.0.209, time stamp: 0x66f3ffc8
Faulting module name: lvrt.dll, version: 24.3.2.4002, time stamp: 0x66f40077
Exception code: 0xc0000005
Fault offset: 0x0000000000b7c7d9
Faulting process id: 0x0x52E0
Faulting application start time: 0x0x1DB5BA3125089AB
Faulting application path: C:\Repos\TED\Software\FATS\Builds\FATS.exe
Faulting module path: C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\2024\lvrt.dll
Report Id: 0fc5224d-13af-429d-8053-146578402cc8
Faulting package full name:
Faulting package-relative application ID:

 

I don't think I'm doing anything exotic.  I have the same thing implemented with arrays and never get an issues.  But figure maps are the quicker/more elegant method.snippet 01.png

 

 

snipet 02.png

 

 

0 Kudos
Message 4 of 4
(183 Views)