LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Export Image to Clipboard Crash

Has anyone else had any problem with the Export Image when Clipboard is the selected target.  It works fine for me as part of the development environment but crashes the program when used as part of a built executable.

(LabVIEW 8.5)
0 Kudos
Message 1 of 17
(4,562 Views)
Hi Chris,
Thanks for posting.  When your built executable is run and causes LabVIEW to crash, is this on the same computer.  I was unable to find any bug reports over this issue.  I would recommend that you recreate the problem with a simple VI and exe and post them here.  I will try to recreate your issue.
Eric A.
National Instruments
Distributed I/O Product Support Engineer
0 Kudos
Message 2 of 17
(4,535 Views)
Hello Eric,

Attached is a zip file with an example VI, the project, and the exectuable -- just in case it's a settings issue with the build.

It's a basic VI with a sine wave being displayed.  A custom menu on the graph has one option - to export to the clipboard.  It works fine in the development operation, but crashes every time as part of an executable.  All other aspects of the executables seem to work fine.

In my package, the crash happens on the same PC and on other PC though I have not tested the example on another PC.  All of my tests have been on modern (<2 years old) Dell PCs with Windows XP.

Chris
Message 3 of 17
(4,524 Views)
HI Chris,
I tried to open your VI but there were some sub VIs missing.  Were you receiving an error number or message?  You said LabVIEW crashes but does LabVIEW give you an opportunity to investiagte it the next time you try to start LabVIEW?  Right now, it either sounds like you might not be including some files in your exe build specifications or it is a bug.  Try to post those missing VIs and I will try to figure out which it is.
Eric A.
National Instruments
Distributed I/O Product Support Engineer
0 Kudos
Message 4 of 17
(4,510 Views)
Eric,

There were no subvis, but one express vi was used to generate a signal.  I removed that; so, it should not be a problem now.  You can build the exe and you'll see it works in the development and crashes as an exe.

Since it only crashes as an exe, LabVIEW does not ask to debug.

Here's the details from the windows crash report:
AppName: export crash.exe     AppVer: 1.0.0.0     ModName: lvrt.dll
ModVer: 8.5.0.4002     Offset: 001bdacf

If I press the debug window, it reports an unhandled exception (see attached pic)

0 Kudos
Message 5 of 17
(4,503 Views)
Hi Chris,
This was reported to R&D (# 4EOEL5Q9) for further investigation. A possible workaround is to print the front panel to a file or to try saving the image to a file. Thanks for the feedback!
Eric A.
National Instruments
Distributed I/O Product Support Engineer
0 Kudos
Message 6 of 17
(4,465 Views)
Try Image Toolbox => Export Bitmap
at:
George Zou
0 Kudos
Message 7 of 17
(4,455 Views)
I also tried using the Applicaiton menu item for export image instead of an invoke node with my own menu item.  It had the same effect.
0 Kudos
Message 8 of 17
(4,449 Views)
Hi Chris,

Just to clarify, were you able to use this as an effective workaround?

Thanks!
Amanda Howard
Americas Services and Support Recruiting Manager
National Instruments
0 Kudos
Message 9 of 17
(4,424 Views)
No, the behaviour was the same (i.e. works in development crashes in EXE for clipboard option only)  whether I used the invoke node or the Application Run-Time Menu item.
0 Kudos
Message 10 of 17
(4,414 Views)