write to jpg make application crash

[JertoZ]

Hello

I am experimenting something weird.

I have build and use the following application for months and everything was going well. At the end of each tests, a snapshot of the main is taken as a log of what happend. I have recently added a tab control with multicolumn listboxs in it and since then, each time I try to take the snapshot of the main screen, my application crash.

It only happen with the build application, not the vi. I have tried to reproduce the same scenario by building a small application with a tab control and multicolumn lisbox in it and it doesn't crash... 

I don't know if there is a way with some error log to know what is causing this crash

Thanks

[Jeremy_B]

Hi,

Can you post the VI itself so we could try it here?

[JertoZ]

Hello Jeremy

It would be kind of hard to do so since the vi is a main vi of about 50 other VIs. On top of that, you will need the ODBC connection that connect to our databases to make it work...

This is why I was wondering if there was an error log that I could consult.

Let me know what could we do.

Thanks

Julien

[Anna_K.]

Hello,

Does this error occur every time that you run the Executable or just sporadically? Did you mention that if you run the VI's in your development environment that there is no crash? Have you tried to rebuild the .exe again? Also I might suggest you take a look at one of our new debugging tools, you may download the evaluation version to try free for 30 days. It is called LabVIEW Desktop Execution Trace Toolkit and can be found at http://www.ni.com/softwareengineering/

Here is the description of this software:

The LabVIEW Desktop Execution Trace Toolkit can help you debug and troubleshoot LabVIEW applications by providing low-level details about the execution of VIs and executables at run-time. You can monitor code and easily identify the source of problems such as reference leaks, memory leaks, unhandled errors, and other issues that can negatively impact the performance and reliability of an application.

Regards,

Anna K.

[JertoZ]

Hello

- Yes, the error does occur everytime I run the executable.

- Yes, there is no crash when I run it in the development environment. 

- Yes, I have tried to rebuild it  several time.

Thanks for the info about the new debugging tool, I will have a look at it and post my results.

Thank you 

[JertoZ]

Ok, I have tried the Desktop Execution tool and I see nothing abnormal.

Is it possible to make it work with a built application? From what I saw, it only works with VIs in the development environment.

Anyway see the jpg to see what is called when the crash occur ( red line section)

Thanks 

[Anna_K.]

Hello,

Could you provide more description of the crash you are seeing?

- Do you receive an error message or does the application just crash and close?

- I see in your block diagram you have the error terminals wired, did you connect all of these to Error Dialogs?

- What is the version of LabVIEW you are using?

- Are you running the .exe on the same machine your developed on?

- What happens if you run it on another machine?

I will create an .exe myself here too and see if I can get any similar behavior. The Execution Trace Toolkit should catch any memory leaks I believe, when looking at your screenshot, these are the last function calls before the crash right?

Regards,

Anna K.

[JertoZ]

Hello

- I have joint a screen shot of the error.

- All my error terminals are wired to error dialogs

- My LV version is 8.6.1 but I had the same problem with 8.6

- I have tried the exe on a couple of machines.

- I have already created another exe with a tab control with muticolumn lisbox in each pages and I didn't obtain the same results.

- Exactly, on the screen shot, you see the last function calls before the crash ( those included by the red line).

If you want I can provide you an installer with my application. I have removed the necessary connections to our databases. However, the file is 76mb so I will need a way to send it to you.

Sincerely

Julien

[Anna_K.]

Hello,

Yeah, I would like to try and run it here and see if we can target a bug. You may upload it to  ftp://ftp.ni.com/incoming. Just let me know what you have called the file. Also, could you send me the error log file mentioned in the error message? Or is it already in the other screenshot?

Regards,

Anna K.

[JertoZ]

Hello

I have uploaded a .rar file named Rampe_V2_Installer.rar on your ftp. I have also joint the error file in the .rar file.

When you will run the .exe, just press the snapshot button in the lower left corner to reproduce the error. Sorry for the large window, I have a 30 inch screen...

Sincerely

Julien