Statechart module: crashes when I want to save state

[dlanger]

I am using the LV Statechart Module (version 8.6.0). LabVIEW crashes when I want to save a state (by clicking "OK" on the state dialog). The crash does only occur if I have some member VIs of a quite large class hierarchy in the state. It does not occur if I for example just wire through the simple error cluster that is part of my state data cluster.

Does anyone have an idea how I could avoid this problem?

The LabVIEW failure log file is attached.

Thanks in advance for any hint.

[aggieNick02]

Looking at this quickly, I do not know the core root cause, but I am guessing that you could work around it by putting your guard or action code into a subVI and using that subVI instead of placing the code directly in the guard/action. Something appears to be going wrong as we try to commit the guard/action VI you created for the state - I am guessing there is a bug in this process as it encounters some of the class stuff you are using, and using a subVI to wrap it will avoid this.

Any chance you can provide the files needed to reproduce this (either here or privately if you prefer). The stack tells me a little bit but we'll have a much better chance of resolving this fully in a future release if we can reproduce it here.

Thanks,
Nick

[dlanger]

Hi Nick

Thanks for your reply. I will try this.

Can you give me your email address (either here or by writing to langer@hifo.uzh.ch if you prefer)? I can then give you access to the site where you can download the full source code.

Best regards,

Dominik

[dlanger]

Update on the issue:
I tried to put the state code into a sub VI. The state dialog can now be closed without crash, but a crash occurs during compiling the statechart. After restarting, LabVIEW does not show the dialog asking to investigate the internal error (which would allow creating the failure log file).

I will now go through all states/transitions of the statechart and replace any code by enclosing subVIs. Hope that helps...

[dlanger]

The sub-VI approach also does not help. Again, as soon as the a subVI contains my class stuff, LabVIEW crashes when the state dialog is closed...

The failure log file contains the same lines as without sub-VI approach:

c:\builds\penguin\labview\branches\Saturn\dev\source\diagram\CopyAccumulator.cpp(36) : DWarn: CopyAccumulator is being destructed without being flushed.
$Id: //labview/branches/Saturn/dev/source/diagram/CopyAccumulator.cpp#1 $

[aggieNick02]

Thanks for the updates; I'm sorry the workaround ideas have not proven effective. I will contact you via email to get info about getting the files and do some investigation.

Thanks,

Nick

[dlanger · Accepted solution]

The problem does not occur anymore in LabVIEW 2009.