Write JPG File of Front Panel with 3D graph Crashes Built Application -- Works OK in Development System

[johnfr]

I have a program that displays 2, 3D graphs on the front panel. Once the graphs are displayed I call the Write JPEG File.vi that is part of the LabView library to save a screen capture of the front panel.

I built this as an application and for several days it worked just fine. After about 3 weeks we attempted to run the program and  the program started crashing at the point it hits the call to Write JPEG File.vi.  When I execute this program in the development system it works just fine. However, if I rebuild it and attempt run it as a built application it still crashes at the same point. So this seems to only manifest with the built application.

I am running on a Windows 7, Bit system on an i5 computer with 8GB of memory. I am running LV2011. The only thing I can guess as the cause is some kind of Windows Update that occurred. The problem seems to have showed up sometime in January 2013.

I am wondering if anyone has experienced problems storing jpg files of 3D graphs?

[G-Money]

Are there any other symptoms like CPU ramping or memory reduction over time?

[johnfr]

Grant,

Not that I have observed. When running program before this bug showed up I had ran dozens of test with no loss of performance or signs of memory leaks. The program is structured as a State Machine so when first test is finish it returns to main menu and waits for user input for Serial Number of next item to test.

After the bug showed up, I start the program and run the test. When the test process finishes I call a subvi that graphs the data and after the graphing process finishs it calls the Write JPG File.vi". As soon as the call to the "Write JPG File.vi" exicutes the program crashes and dumps me out to the Window Operating system. It seems to actually close the program. I have "Allow Debug" turned on for the build process and when the crash occurs there is now error message.

By the way, this program is built as a 64 Bit application.

[zou]

Have you tried other color depth?  For example use the "true" color, ie. 24 bit, instead of 256 colors?

[Yamaeda]

It could be a path issue internally in the .exe. Try activating Use LV8.2 file structure or what it's called when building the application and see if it works.

/Y