LabVIEW Crash while using LuaVIEW toolkit v2.0.0beta-4
TimV
Rolf Kalbermatter
Hello Tim
I took a look at this problem and cannot reproduce it on my computer system. Do you have an more specific details about how to reproduce it?
What I did was trying to load and execute the script “FileOrDirExists.lua” in the Task Manager using the “Run Local (F3)” function. I started the Task manager both directly from the Tools menu as well as from your LuaVIEW2tools.vi project.
Did you try it on a single system or on more than one of them? If you tried it on one single system, is there a chance that you could try it also on another one?
Sincerely
Rolf Kalbermatter
--
You received this message because you are subscribed to the Google Groups "LuaVIEW" group.
To unsubscribe from this group and stop receiving emails from it, send an email to luaview+u...@googlegroups.com.
To post to this group, send email to lua...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/luaview/524507ec-4e6b-4e04-bb85-3d16a079d48d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
TimV
My apologies for this overdue response.
>> What I did was trying to load and execute the script “FileOrDirExists.lua” in the Task Manager using the “Run Local (F3)” function. I started the Task manager both directly from the Tools menu as well as from your LuaVIEW2tools.vi project. <<
This was exactly how I produced the problem as well, and LabVIEW crashed regardless of which method started the LuaVIEW Task Manager (upon try to run a script).
>> Did you try it on a single system or on more than one of them? <<
I have now tried this on a second system, and it crashes there as well. Same environment: LabVIEW 2011/SP1 (32-bit) on Windows 7/SP1 (64-bit).
I have also been able to reproduce the LabVIEW crash by running other small and simple Lua scripts using "Run Local (F3)", AND even with a single line Lua chunk of "print('hello')" using "Run Quick (F2)".
After the crash, all LabVIEW windows close by themselves, and there are then zero LabVIEW applications running as viewed on the "Applications" tab of WINDOWS Task Manager; however the "Processes" tab of WINDOWS Task Manager still shows one instance of LabVIEW.exe. Re-launching LabVIEW after the crash creates a second instance of a LabVIEW.exe process, leaving the original process orphaned from any UI element (no window claims it).
Tim
Rolf Kalbermatter
Hi Tim
I’m in the process of preparing a new beta version for LuaVIEW as intermediate solution until the final release. Basically all the problems you encounter are likely caused by the fact that the Beta DLL has an expiration date. When that happens it tries to display a dialog to inform you about this but this seems to fail catastrophally in recent LabVIEW versions. Not exactly sure about the details but it seems not safe anymore to open a dialog from within a DLL anymore as LabVIEW then gets into a dead lock somehow, probably between the UI system in which the dialog is supposed to occur and the actual execution system in which the LuaVIEW DLL is executing.
I’ll need to make a few more changes to the documentation and plan to release a last Beta with extended expiration date until Friday of this week.
Sincerely
Rolf Kalbermatter
--
You received this message because you are subscribed to the Google Groups "LuaVIEW" group.
To unsubscribe from this group and stop receiving emails from it, send an email to luaview+u...@googlegroups.com.
To post to this group, send email to lua...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/luaview/428d1b84-ac27-49c5-90e2-d89c7b626819%40googlegroups.com.