06-09-2026 07:45 PM
There's a problem I have been noticing very intermittently in LabVIEW. It's been on multiple PCs and multiple editions (2021 32 bit, 2024 32 bit).
What will happen is that I try to open and use Quick Drop. I press control-space, and then start typing. 98% of the time it works as expected, but that last 2% of the time it lets me type in one or two characters, then the whole thing becomes unresponsive for 5-10 seconds (not even any more letters are being entered in the text field), then it resumes and starts working again, with anything I typed during the freeze getting lost. This really throws off my programming flow, so much so that I set up Process Monitor to run, filtered for events coming from LabVIEW.exe, so that I could wait for it to happen and then check what LabVIEW was up to in the meantime.
This afternoon I was finally able to have the issue occur under LabVIEW 2024 while Process monitor was logging, and I had just typed the "t" in "tc" to put down a True constant, and this is a rough summary of what LabVIEW seemed to spend its time doing:
4:27:29.0 to 4:27:29.2: Load a bunch of stuff from "LabVIEW 2024\resource\dialog\QuickDrop" plus some assorted VI files and checking the VI object cache file - this seems expected
4:27:29.3 to 4:27:29.5: Look through all the .mnu files in "LabVIEW 2024\menus\" as well as many "menus" directories under "Program Files\NI\LVAddons\" - makes sense, needs to populate the list in the QD window
4:27:29.6 to 4:27:35.6: Reads of approximately 2000 VI files, the vast majority of which should be completely unrelated to Quickdrop... Approximately 1500 from vi.lib and 500 from the LVaddons folder.
So clearly it's that last section lasting (this time) about 6 seconds. I had configured Process Monitor to log the duration of each access, and when sorting by that to find what took the longest to access, I found that by far the files in "LVaddons" took longer to access.
Average of the ~1500 files in vi.lib: 0.5 ms per file
Average of the ~500 files in LVAddons: 7.8 ms per file
It's a very clear delineation, as well. The LVAddons files were all from 6.9 ms to 22.7 ms, while all the vi.lib files were 0.39 ms to 0.9 ms.
There's other operations in there as well that didn't take much time (assorted registry checks, DLL calls, etc.) but nothing with long durations or in such quantity as to make up a significant portion of the remaining time.
As such, my best guess is that whatever it's doing is something it doesn't do all the time, but when it does do it, it takes far longer on the LVAddons for some reason.
Anyone have any idea why this might be happening and how to stop it? I did find this:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000001E9aiCAC&l=en-US
However, that article is about quick drop taking a while to appear. It appears just fine, it's the part after I type in a letter or two that freezes up for a bit.
06-10-2026 10:21 AM
Total stab in the dark here but I wonder if it's recompiling your LVAddons files, but not your VI.lib files.
I've had some weirdness every once in a while that seems to mark libraries I've installed from VIPM as "changed" and asks me to save them, claiming they've been recompiled for some reason. I haven't been able to consistently reproduce this behavior to understand why, as I'm not modifying those VI's at all.
Could you try doing a Mass Compile on your LVAddons directory and make sure they all compile successfully to get them into your cache?
06-10-2026 10:58 AM
Anti virus?
06-10-2026 11:08 AM
Who remembers Roseanne Roseanna-danna? "It's always something -- if it's not one thing, it's another".
Bob Schor
06-10-2026 11:21 AM
I have a few suggestions:
1) Make sure you're running LabVIEW 2024 Q3 with all the latest patches.
2) Mass compile [LabVIEW 2024]\resource\dialog\QuickDrop
3) Click 'Configure' in the Quick Drop window, go to the 'Options' page, and make sure Enable relevancy-based search is UNCHECKED
4) Go to Tools > Options > Controls/Functions Palettes > Loading and select 'Load palettes during launch'. This will make your LabVIEW launch take longer, but will also ensure all palette info is already loaded once you start using Quick Drop.
06-10-2026 12:18 PM
@Darren wrote:
I have a few suggestions:
1) Make sure you're running LabVIEW 2024 Q3 with all the latest patches.
2) Mass compile [LabVIEW 2024]\resource\dialog\QuickDrop3) Click 'Configure' in the Quick Drop window, go to the 'Options' page, and make sure Enable relevancy-based search is UNCHECKED
4) Go to Tools > Options > Controls/Functions Palettes > Loading and select 'Load palettes during launch'. This will make your LabVIEW launch take longer, but will also ensure all palette info is already loaded once you start using Quick Drop.
1) I was running 2024 Q3 24.3.2f2, freshly installed a month ago from the offline installer ISO. I would have thought that was the most recent version so I went to NIPM to prove it was and... it wasn't. I'm now on 24.3.6f6. According to these notes the update from 2 to 6 should only have fixed some crashes and vulnerabilities, and doesn't seem to have updated any QuickDrop VIs, but it's hard to be certain it won't help.
2) I'll try that, in addition to mass compiling the LVaddons directory as suggested above.
3) It wasn't checked.
4) I've changed it (was "in background") but this doesn't seem like it should be the issue unless they "expire" somehow? This issue happened at 4:30ish in the afternoon, after I'd been running LabVIEW for over 2 hours straight and had probably opened QuickDrop 50 to 100 times by then.
Anyway, I'll give all that a shot and then resume development... but it can be hard to "prove" that a fix has come out for an event that occurs fairly rarely. I can definitely report back if it doesn't work...
06-10-2026 12:39 PM
@Yamaeda wrote:
Anti virus?
Just saw this question nestled in the rest of the replies.
My company just uses standard Microsoft Defender. Nothing in use that's notoriously bloated like McAfee or whatever.
06-10-2026 12:57 PM
@Kyle97330 wrote:
@Yamaeda wrote:
Anti virus?
Just saw this question nestled in the rest of the replies.
My company just uses standard Microsoft Defender. Nothing in use that's notoriously bloated like McAfee or whatever.
We use Defender, too, and for some reason mine is INCREDIBLY overzealous and has been scanning everything all the time 😞
06-10-2026 04:21 PM
@BertMcMahan wrote:
@Kyle97330 wrote:
@Yamaeda wrote:
Anti virus?
Just saw this question nestled in the rest of the replies.
My company just uses standard Microsoft Defender. Nothing in use that's notoriously bloated like McAfee or whatever.
We use Defender, too, and for some reason mine is INCREDIBLY overzealous and has been scanning everything all the time 😞
I just checked our Windows Defender exclusion list. My company had the 32 bit folder excluded ("C:\Program Files (x86)\National Instruments"), but not the 64 bit folder ("C:\Program Files\National Instruments") or the shared addons folder ("C:\Program Files\NI"). I've gone ahead and added both of those on my local PC since I have local admin rights on it.
That, combined with the mass compiling in 2 different places, the LV patch I added, and the palette load setting change, gives 5 different things I have now done to attempt a fix here.
I'll report back probably in hours or a few days if I still have the problem. If I can go 2-3 weeks without it happening, I'll call it a fix as well, though it will be difficult to zero in on just one of them as a solution since I did them all.