ThomasGutzler Posted June 23, 2020 Report Share Posted June 23, 2020 Please make a 64bit release of VIPM Quote Link to comment Share on other sites More sharing options...
0 Jim Kring Posted June 23, 2020 Report Share Posted June 23, 2020 Hi @ThomasGutzler. Thanks for the great idea! I'm curious what you need 64-bit support for, specifically? Are there any problems created by having VIPM for Windows be a 32-bit application? Would making it 64-bit help in specific ways? Thanks for letting us know. Quote Link to comment Share on other sites More sharing options...
0 ThomasGutzler Posted June 23, 2020 Author Report Share Posted June 23, 2020 Always forward, Jim I don't want to bring up the "increased performance" argument. I mean, we're using LabVIEW after all. Nobody who's using LabVIEW can seriously play the performance card. I regularly see VIPM using over 1GB of memory and sometimes crashing with an "out of memory" error - although that might be due to the ridiculous 4GB of total memory available on that machine. How long before that goes to 2GB, 3GB? We've had 64bit on windows for 15 years now. I think it's time to move on. At least give us the option. Surely VIPM isn't depending on modules that don't exist in 64bit land 1 Quote Link to comment Share on other sites More sharing options...
0 Jim Kring Posted June 23, 2020 Report Share Posted June 23, 2020 Hi Thomas, Actually, we use some 32-bit shared libraries, including OS libraries and also some 3rd party libraries, like the OpenG Zip Tools. For the MacOS beta, VIPM migrated to using command line zip/unzip tools and dropped a couple minor usability features that maybe nobody will notice (like extracting lvlib/lvclass icons from the XML file, which requires zlib deflation). However, for MacOS, we figured it was better to have things mostly working OK in 64-bit than not at all. For Windows, we wouldn't want to lose any functionality. I hear you about the memory limit issue. I hope that's helpful information, and please know we're not hesitating to explore 64-bit, for no good reasons. Regards, -Jim 1 Quote Link to comment Share on other sites More sharing options...
0 ThomasGutzler Posted August 2, 2020 Author Report Share Posted August 2, 2020 Our build server fell over last Friday. Nobody noticed, this morning I am greeted with this: This is how it started: =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 05:29:08 PM = Automated Message Start = Error 2 occurred at Obtain Queue in JKI_LVConfig__jki_lib_configuration_file.lvlib:1188A4A91C005F423D89358A8C95F362->4F9D0428213F8F95FE3 A745133E46203->FF473C6B63ADACAEF90D52E8AFBDC45F->246E5055266A40F567071DB843B25FE8->1C008B1C8A190D0D7 176E93799F7534B->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001->5AB213F9CD1875C24859DB C20A7CDE64->VIPB_API.BuildAndPackageLibrary.vi->VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58->41AC743D0ED402FF42A432FD77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = User Defined Message Start = VI Package Builder Error = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0-> VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58-> VIPB_API.BuildAndPackageLibrary.vi-> 5AB213F9CD1875C24859DBC20A7CDE64-> VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 05:29:10 PM = Automated Message Start = Error 2 occurred at Obtain Queue in JKI_LVConfig__jki_lib_configuration_file.lvlib:1188A4A91C005F423D89358A8C95F362->4F9D0428213F8F95FE3 A745133E46203->FF473C6B63ADACAEF90D52E8AFBDC45F->246E5055266A40F567071DB843B25FE8->1C008B1C8A190D0D7 176E93799F7534B->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001->5AB213F9CD1875C24859DB C20A7CDE64->VIPB_API.BuildAndPackageLibrary.vi->VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58->41AC743D0ED402FF42A432FD77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== And after that it's just this: =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Monday August 03, 2020 at 09:13:31 AM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== and continuing to fill. Task Manager tells me there are still 2GB of memory available Quote Link to comment Share on other sites More sharing options...
Question
ThomasGutzler
Please make a 64bit release of VIPM
Link to comment
Share on other sites
4 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.