LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

crash in Typemgr line 1018 (bad typeID) when moving VIs out of a flatsequence

I have found a reproducibel crash for LabVIEW7 (english) on Win2k (german). It was tested on two distinct machines (PIII/450 w.480 MB RAM and PIV /2000 w. 512 MB).
The crash occures during editing:
* Open the provided example code and go to the BD
* Mark all objects inside the flat sequence
* Move all marked objects out of the sequence.
LabVIEW will use 100 % of CPU and an extra of about 2-3 MB of RAM and will finally crash after some seconds:

Fatal error in typemgr.ccp line 1018

The log says 'bad typeId'

This bug can easily be circumvented. No reply necessary.
Download All
0 Kudos
Message 1 of 5
(2,650 Views)
I've got exact the same behavior!
0 Kudos
Message 2 of 5
(2,650 Views)
Lul,
I was able to reproduce this behavior.
The Discussion forum is not the best way of reporting crashes to NI.
Could you generate a service request on ni.com/ask and send this crash report to NI directly.
Thanks

Zvezdana S.
National Instruments
0 Kudos
Message 3 of 5
(2,650 Views)
and...
When you restart LabVIEW after this crash, you will get a dialog informing you about this error. Select to investigate the error, and locate the error log file created. When you contact NI, send the log file and the VI.
Zvezdana S.
0 Kudos
Message 4 of 5
(2,650 Views)
Zvesdana,

I know both facts. But as I wrote: 'No reaction necessary', there is no need for neither Ni nor me to react immediately. Just wanted NI to know...
Whenever I request support, it is always redirected to NI Germany. And this produces some overhead I wanted to avoid in this case.
I hope that _you_ have put this bug onto the right list ;-))
Greetings from Germany!!
0 Kudos
Message 5 of 5
(2,650 Views)