We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reported here: https://forums.jki.net/topic/2743-jki-sm-problem-with-jki-sm-editor/
I've got a problem with JKI SM Editor (JKI SM ver. 2018). In one case, it increases the CPU resources consumption. The procedure is as follow: 1. Open New VI or existing VI with JKI SM. 2. Open block diagram. Open JKI SM Editor. 4. Close front panel of the VI. CPU usage increases - in my case (i5-4210M) up to 38 - 40%. Have to reset the LabVIEW. Has anyone observed silmilar behaviour?
I've got a problem with JKI SM Editor (JKI SM ver. 2018). In one case, it increases the CPU resources consumption. The procedure is as follow:
1. Open New VI or existing VI with JKI SM.
2. Open block diagram.
4. Close front panel of the VI.
CPU usage increases - in my case (i5-4210M) up to 38 - 40%.
Have to reset the LabVIEW.
Has anyone observed silmilar behaviour?
The text was updated successfully, but these errors were encountered:
Problem
Solution
Sorry, something went wrong.
Fix for Issue #83 - JKI SM Explorer VI keeps running when target VI F…
7630ebc
…P is closed Now ignoring errors when closing the JKI SM object reference.
Fixed. Released with JKI State Machine. See here:
#83
No branches or pull requests
Reported here: https://forums.jki.net/topic/2743-jki-sm-problem-with-jki-sm-editor/
The text was updated successfully, but these errors were encountered: