06-24-2019 09:08 AM
Hello,
I am rewriting a project in LabVIEW 2017 32bits, it used to work in 64bits. But one dll used for hardaware communication is not available in 64 bit version.
My project is based on multiple levels of PPL whith different level of dependencies. Parents class are containe in higher level PPL.
One of the projects to build a PPL cannot open any more. It used to crash and generate a report but now it is not even caught by the crash report. Sometimes it asks me when If I want to handle the crash when labView restarts.
I've attached the code of the project. The 3 PPL required to compile this project and a crash report.
I've run out of things to try to continue investigating. The project that I can't open is \plugin Generique\Plugin Generique.lvproj
Using LabVIEW 2017 32bit
Windows 10.
06-24-2019 10:15 AM
Did you try to clear the compile cache?
06-24-2019 10:55 AM
I didn't know this option before you mentionned it.
I've just cleared the compile cache and reloaded my project, this doesn't change anything the project doesn't load and labVIEW crashes.
06-24-2019 12:18 PM
This could get ugly. If you use a repository for your software - as everyone should - it could be that your project file got merged and is now corrupt.
06-25-2019 01:36 AM
Yes I am using a repository. But I am the only one using and I didn't use merge functions.
Even starting a new project and adding my elements one by one,(PPL, lvlib) is fine. as soon as I try to reopen the project, I have a crash.
This represents 3 month work and going back in my repository does not help.
It seems to me the problem is with the PPL as the report suggests that the vi are broken inside the PPL.
06-25-2019 03:26 AM
I just thought I'd mention the project file merge thing because once I forgot and accidentally worked on the same project from two different places without updating, and SVN ended up merging the two versions of the project file. Fortunately it was such a minor change that I was able to choose one version over the other and fix it. (Now SVN knows to treat the project file as a binary.)
I hope it's not too painful to fix. 😞
06-25-2019 03:53 AM
@didje007 wrote:
Yes I am using a repository. But I am the only one using and I didn't use merge functions.
Repos can try to do you a favor and merge for you... Esp. files that are recognized as text, like .lvproj, .lvclass, etc.
06-25-2019 03:56 AM
@didje007 wrote:This represents 3 month work and going back in my repository does not help.
So what used to work isn't working anymore?
That makes me thing the code is OK, and it's your environment...
Is everything in your repo, or are the PPLs\lvlibs outside of this repo?
You could of course create a new project, and then add only one thing, save, check. Maybe you'll find out which element causes the crash.
06-25-2019 03:59 AM - edited 06-25-2019 04:08 AM
Those logs are pretty incomprehensive. but "Journal.lvlibp: Space Constant.vi"* keeps popping up.
Not sure what to do about it, but if you can rename, delete or revert it somehow, it's worth a shot.
* Witout the space between : and S, but that shows up as :S...
06-25-2019 04:34 AM
Space Constant.vi is not one of my VI,
It seems to be included in Get LV Class Path.vi