Jim Kring Posted November 15, 2022 Report Share Posted November 15, 2022 Issue Over the past 24 hours there was a VIPM issue where the client was showing out of memory errors. This has been resolved. How to Fix Please try restarting VIPM Desktop and refreshing your package list (the refresh button) a couple times. If you still have problems, try deleting the “C:\ProgramData\JKI\VIPM\cache” folder and restart VIPM. Background The problem was on the vipm.io server — the the repository index file had grown exponentially large due to a character encoding bug that was causing one special character of a certain package name to get duplicated on every package release (and the duplications kept getting duplicated). The repository index file grew to ~64 MB (it was growing in powers of 2... 4, 8, 16, 32, 64) and then caused all the VIPM Desktop clients to have out of memory errors! Some Lessons Learned The littlest bug can sometimes cause big problems — like a mosquito when you’re trying to sleep. Exponential Growth sneaks up on you and then gets out of control very fast. The out of memory error in VIPM Desktop showed several places in the codebase that could be further optimized as the total number of packages continues to grow. The LabVIEW Configuration File (INI) VIs don’t handle extremely large files well. Parallel For Loops allow work to be done on large arrays much faster (operating on elements in parallel), but it also takes more memory. There is a trade off. We are looking into a build of VIPM in 64-bit LabVIEW to make more memory available, when needed. 2 Quote Link to comment Share on other sites More sharing options...
Franklin.Von Posted November 16, 2022 Report Share Posted November 16, 2022 Hi Jim What is the total solution of the 'No enough memory complete the operation' issue ?? Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted November 16, 2022 Author Report Share Posted November 16, 2022 The solution was to remove the extra/duplicate data in the repository index and fix the bug that caused it to appear in the file. This is a server issue (it was sending the client too much data) and not related to VIPM Desktop itself. Quote Link to comment Share on other sites More sharing options...
Franklin.Von Posted November 16, 2022 Report Share Posted November 16, 2022 (edited) Hi Jim What need I do anything ?? How to do it ?? Edited November 16, 2022 by Franklin.Von Quote Link to comment Share on other sites More sharing options...
Anbarasan Posted November 16, 2022 Report Share Posted November 16, 2022 How to the changes in repository index Quote Link to comment Share on other sites More sharing options...
Allen Hsu Posted November 16, 2022 Report Share Posted November 16, 2022 Problem is solved! If VIPM still crash, try to delete files in C:\ProgramData\JKI\VIPM\cache, and open VIPM again. 1 Quote Link to comment Share on other sites More sharing options...
Dmytro Posted November 16, 2022 Report Share Posted November 16, 2022 Problem solved after clearing the C:\ProgramData\JKI\VIPM\cache folder, thank you. Now peak memory consumption is about 740 MB. Quote Link to comment Share on other sites More sharing options...
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.