Re: Crash of LabVIEW executeable after some hours

[Lenin]

Thanks for your comments.
NI germany has offerd me to get a test version of LabVIEW 7.0
(including application builder). This will be my next try. As I
mentioned in the posting before, I already do testing with the
executable with multithreading disabled (ESys.StdNParallel=0). At the
moment the system runs in this configuration for about 24 hours, but
its to early to say "I've got it!". Anyway, most of the application is
straight LabVIEW. There are some minor calls to DLL's, but these have
been prooven in other applications over years. I don't use ActiveX
controls. So my opinion still is, that the problem is related to
LabVIEW (runtime) itself. And additionally it can't be a solution for
the future to disable multithreading to get a stable application. And
at the end, that the crash always occurs at the same LabVIEW internal
code position is an indicator for me, that my opinion can't be so
wrong. Is'nt there anybody in Austin who can take a look at source
code of the internal function "CancelOnOccur" to help tracking down
the problem. I hope that NI is interested in increasing its products
quality...

Re: Crash of LabVIEW executeable after some hours

[Lenin]

Addendum:
The above described failure does not occur, when multithreading for
the LabVIEW execution system is disabled. It looks like that there is
something non-threadsave inside LabVIEW.

I am curious about your comments.

Crash of LabVIEW executeable after some hours

[Lenin]

Hi to all,
I'm developing a LabVIEW program for a long term monitoring
application of serial (RS232) devices. On the target system the
program runs as executable. At start-up everything runs fine. After
several hours (usually 1..3) the application crashes with an access
violation. I did a lot of "debugging" on executable level, because the
error seems not to occur in the development environment. I found out,
that the fault has nothing to do with the serial communication,
because it occurs also in a "demo mode", where no communication with
devices is performed. I studied the Dr.Watson log files and found out,
that the fault occurs always at the same code position. (See below for
details.) The fault occurs under LabVIEW 6.0, 6.0.2 and also 6.1,
(resp. the according runtime). At the moment The Dr.Watson log
suggests, that the LabVIEW internal function "CancelOnOccur" performs
a jump to address 0x, what of course will cause a GPF. The
symbol for this function can be found in the runtime DLL's as well as
the LabVIEW.exe. The development system and the target are  Win2k
machines with all available patches/updates including SP4. Here are
some interesting parts from the Dr.Watson Log (sorry its in german):

Anwendungsausnahme aufgetreten:
Anwendung:  (pid=832)
Wann: 27.03.2004 @ 12:02:28.522
Ausnahmenummer: c005 (Zugriffsverletzung)

*> Systeminformationen <*
Computername: - removed for privacy -
Benutzername: - removed for privacy -
Prozessoranzahl: 1
Prozessortyp: x86 Family 6 Model 8 Stepping 6
Windows 2000-Version: 5.0
Aktuelles Build: 2195
Service Pack: 4
Aktueller Typ: Uniprocessor Free
Firma: - removed for privacy -
Besitzer: - removed for privacy -


.

Statusabbild für Threadkennung 0x4a0

eax=00ca6830 ebx=0003 ecx=00014988 edx=00ca6830 esi=
edi=f1d1
eip= esp=01fcff14 ebp=01fcff30 iopl=0 nv up ei ng nz
ac po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=
efl=0296


Funktion: 
FEHLER -> ???
0001 ???
0002 ???
0003 ???

*> Stack Back Trace <*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
01FCFF10 3023F32E F1D1 0001 00D30368  ! 
01FCFF30 300797D2 7FB84F88 7FE5AEA8 0001 7FEC01B8 !CancelOnOccur 
01FCFF50 300C5AAC 7FE5B0D8 0001 7FEC01B8 0001 !GetSetLVInfo 
01FCFF88 30075DEE 7FEC01B8 0001 77E9BFF2 00CC0DF8 !ImaqReturnIDs 
01FCFFA0 3026E759 7FEC01B8 30352068 0012E0EC 01FCFFEC !ConfigExec 
01FCFFB4 77E7B382 00CC0DF8 30352068 0012E0EC 00CC0DF8 !GetTextRect 
01FCFFEC  3026E730 00CC0DF8  00505A4D
kernel32!lstrcmpiW

*> Raw Stack Dump <*
01fcff14  2e f3 23 30 01 00 d0 f1 - 01 00 00 00 68 03 d3 00 
..#0h...
01fcff24  00 00 00 00 30 68 ca 00 - 88 67 93 7f 50 ff fc 01 
0h...g..P...
01fcff34  d2 97 07 30 88 4f b8 7f - a8 ae e5 7f 01 00 00 00 
...0.O..
01fcff44  b8 01 ec 7f 00 00 00 00 - 01 00 00 00 88 ff fc 01 

01fcff54  ac 5a 0c 30 d8 b0 e5 7f - 01 00 00 00 b8 01 ec 7f 
.Z.0
01fcff64  01 00 00 00 b8 01 ec 7f - f8 0d cc 00 10 2d cb 7f 
.-..
01fcff74  94 3d c4 7f 00 00 00 00 - 00 00 00 00 00 00 00 00 
.=..
01fcff84  00 00 00 00 a0 ff fc 01 - ee 5d 07 30 b8 01 ec 7f 
.].0
01fcff94  01 00 00 00 f2 bf e9 77 - f8 0d cc 00 b4 ff fc 01 
...w
01fcffa4  59 e7 26 30 b8 01 ec 7f - 68 20 35 30 ec e0 12 00  Y.&0h
50
01fcffb4  ec ff fc 01 82 b3 e7 77 - f8 0d cc 00 68 20 35 30 
...wh 50
01fcffc4  ec e0 12 00 f8 0d cc 00 - 00 80 fd 7f 05 00 00 c0 

01fcffd4  c0 ff fc 01 60 fb fc 01 - ff ff ff ff b4 1b ec 77 
`..w
01fcffe4  f0 2a e7 77 00 00 00 00 - 00 00 00 00 00 00 00 00 
.*.w
01fcfff4  30 e7 26 30 f8 0d cc 00 - 00 00 00 00 4d 5a 50 00 
0.&0MZP.
01fd0004  02 00 00 00 04 00 0f 00 - ff ff 00 00 b8 00 00 00 

01fd0014  00 00 00 00 40 00 1a 00 - 00 00 00 00 00 00 00 00 
[EMAIL PROTECTED]
01fd0024  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 

01fd0034  00 00 00 00 00 00 00 00 - 00 01 00 00 ba 10 00 0e 

01fd0044  1f b4 09 cd 21 b8 01 4c - cd 21 90 90 54 68 69 73 
!..L.!..This

Any ideas fromm other users?
Is there someone at NI who can support this issue? 

If there is more information needed, I can provide it.
Thanks in advance!

Best Regards