LabVIEW
Application crashes on launch after switching to Labview 2025 Q1
Hello, I would like to switch to Labview 2025 from Labview 2024 Q3. My application works fine in debug mode, can be builded, however when I lauch .exe, it crashes. NI Error Reporter shows me this window.
When I open .dmp file in Visual Studio and run Diagnostic Analysis I get these infomation.
Application worked perfectly in Labview 2024 Q3, this behaviour never occured. I am using 32-bit Labview. Google did not help. I tried to reinstall Labview 2025. Did not help. Then I uninstalled all NI software and installed just Labview 2025, unfortunately it also did not help. Can you help?
That's the runtime engine itself crashing, not his program. I doubt it's a race condition in his code.
Can you uninstall all NI stuff, reinstall 2024, rebuild, and check it?
Also, can you add some stuff to your code to delay how things initialize and how functions run? You may be able to nail down a specific function call if, for example, you're calling some dll's at the start of your code that might not play nicely with the new version.
Also... by any chance are you using classes, Actor Framework, reentrant VI's, etc? I ran into a bug that NI support helped me with that involved maps, classes, and reentrant VI's.
Hello BertMcMahan, I unistalled everything, installed 2024 Q3, new executable works just fine.
I also did some testing before that. I was curious about our internal .dll, because I saw it's name in small window when executable build in Labview 2025 tried to load before it crashed.
3 out of our 4 Labview applications fail to run executable built in Labview 2025. The application which can build and run executable in Labview 2025 do not use our internal dll. So this could be likely the issue however like said I never had this kind of problem in Labview 2024 or labview 2017 before that. Is this bug in Lalbview runtime or can this be fixed from my side?
I am using Windows 11 (forgot to mention).
Can you try removing your dll from the build? Or at least ensuring the dll isn't called automatically at the start of the program? If calling the dll is the issue, then you could try ensuring it's NOT called until you click something intentionally in your program. If it crashes when you click it, then you know it's your dll.
Unfortunately I have zero knowledge of fixing dll issues, other than knowing that bitness is a "Big Deal" and that pointer sizing is very important. Beyond that... just hope rolf comes by 🙂
So I did some testing again. Completaly removing dll is not possible, it is too crucial for application. I made screenshot of first frame of main .vi. I removed everything complex (closing dll class references, making references of buttons, getting version of project) from start of application (red reactangle). Unfortunately application still crashes and I don't even get message box (blue reactangle). So I think that application doesn't even fully load, it crashes before that.
Bert, thank you for advice, do you know what else could help?
When you run the exe, and it crashes, you may get a file in the %temp% directory that can provide more information. It would be called something like "[ExecutableName]_32_25.1.f.1...txt.
It should show the same Access Violation you saw in Visual Studio, but may provide more information to point to the VI, or if the dll is truly the issue.
Is the DLL a .NET one? Or C or something else?
