Jump to content

Recommended Posts

Hello,

When I delete virtual folder in me project this results in a LabVIEW crash.  This happens in windows 10 and in windows 7, even if I have a project with only empty virtual folders and I start deleting them.

Are there other people where this is happening too?

Link to post
Share on other sites

The following VI creates virtual folders and then deletes them from the project. Running this VI results in LabVIEW crashing on multiple systems in our company. The systems are running LabVIEW 2017, 2017 SP1 or 2018 (32 and 64bit) on Windows 7 and Windows 10. We also have some systems that don't crash.

 

Would be nice if some people here can try it, it would give us some additional data to send to NI.

 

The VI is saved in LV2017, I could save it for a previous version if needed. 

LabVIEW Crasher Virtual Folders.vi

Virtual Folder Test.lvproj

Link to post
Share on other sites

I was unable to get a crash. I gave up when it indicated about 5000 deletions. Did I need to do more?

LabVIEW 2017 both 32 & 64 bit on Windows 10. (Note: not SP1)

Edited by ShaunR
Link to post
Share on other sites

You might have some VI that are not saved may be read only that reference a VI in that folder even this VI do not exist... 

The question is why those virtual folder are empty? what is the last action before?

It is possible that you deleted library as well that where on those virtual folder.

Link to post
Share on other sites

Thank you for testing,

On our systems it usually happens well before the 500 deletions using this VI, when doing it manually in the project explorer it usually within 10 attempts

The application this is used in is a sequencer application that fills a virtual folder with VI's that are used in the sequence to add them to the build specification. After the build we need to clean the project so we need the folder empty. First we removed all the members of the folder one-by-one but we ran into problems when a VI used in the sequence was also used in the sequencer application itself, it could not be deleted then. Deleting the entire folder and recreating it did work but we sometimes we had labview crash as soon as we try to build.

we can reproduce the crash by simply creating a new project, create a (empty) virtual folder and delete it. For some reason the crash is a lot more frequent when doing it manually as opposed to the programmatically creating and deleting 

 

I have added a crash log for those interested, there are quite a bit of DWarn's in there:

DWarn 0x0E697B77: Caught exception in ExtCode call!
e:\builds\penguin\labview\branches\2017\dev\source\execsupp\ExtFuncRunTime.cpp(92) : DWarn 0x0E697B77: Caught exception in ExtCode call!

DWarn 0x50CBD7C1: Got corruption with error 1097 calling library mxLvProvider.mxx function mxLvApi_SetIconOverlaysBatch
e:\builds\penguin\labview\branches\2017\dev\source\execsupp\ExtFuncRunTime.cpp(275) : DWarn 0x50CBD7C1: Got corruption with error 1097 calling library mxLvProvider.mxx function mxLvApi_SetIconOverlaysBatch

DWarn 0x50CBD7C1: Got corruption with error 1097 calling library mxLvProvider.mxx function mxLvApi_ServerSite_UpdateItemUIBatch
e:\builds\penguin\labview\branches\2017\dev\source\execsupp\ExtFuncRunTime.cpp(275) : DWarn 0x50CBD7C1: Got corruption with error 1097 calling library mxLvProvider.mxx function mxLvApi_ServerSite_UpdateItemUIBatch

lvlog.txt

Edited by BramJ
Added crash log
Link to post
Share on other sites
7 minutes ago, BramJ said:

when a VI used in the sequence was also used in the sequencer application itself, it could not be deleted then. Deleting the entire folder and recreating it did work

That's your problem then. You've whipped the carpet out from under LabVIEW. Namepace the VIs in the sequencer.

Link to post
Share on other sites

A simple solution for you would be to work with a copy of the project and then whatever you want except deleting... then no crash and you project original remain clean...

by the way, project and library are only .xml files.

Benoit

Link to post
Share on other sites

Searched a bit further and it seems the crash is caused by the Viewpoint TSVN toolkit. Removed it and it works just fine. re-install it and it crashes again.

Odd thing is... we have one system with the same set of toolkits, including TSVN, and that system doesn't crash

Link to post
Share on other sites
4 hours ago, BramJ said:

Searched a bit further and it seems the crash is caused by the Viewpoint TSVN toolkit. Removed it and it works just fine. re-install it and it crashes again.

Odd thing is... we have one system with the same set of toolkits, including TSVN, and that system doesn't crash

I use TSVN and it didn't crash on my machine.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By Elancheran
      Hi Everyone,
            I am trying to play the video in reverse decrementing the frame number in IMAQ Read Frame function. Its working but the result is very choppy as every frame takes significant time to load, but when I just increment the frame number and play the video forward, its executing without any problem. I have attached the VI and info regarding the video, could you guys please let me know why I am having problem when I am trying to display the video in the reverse order.
      Playing AVI file.vi

    • By bjustice
      Hey guys!
      So, I've installed LabVIEW 2017 and I'm starting to play around with it.  Malleable VIs are cool!  (No more giant OpenG toolkits where there are 10 instances of the same VI for multiple datatypes.)
      Another cool thing that I've observed is that the example "sort 2D Array" function can support a scalar and an array input for index.  Upon further digging, there appears to be an interesting disable structure that intelligently selects the upstream input that yields non-broken code. 
      Does anyone have more information about this structure?  Is this related to the experimental structure that Hooovah talked about in his Xnodes presentation at NI week?  I'm just curious if this is stable... and if I can start using it... and it there is any documentation on it that would tell me how to use it.
       
       


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.