Fatal Internal Error: "drawmgr.cpp" line 3793

[Cheese11]

Hi everybody,

I was just clicking around in Labview and then the next error came up:

Fatal Internal Error: "drawmgr.cpp" line 3793

I restarted Labview and the error was gone.

But I want to know what the problem was, if it will appear again.

I hope you can help me with this problem.

Greets,

Kenny

[Cory_K]

What exactly were you doing when the crash occured?

From what it looks like here, there is some type of memory leak in a few of the plotting functions mentioned in that thread.

Are you using any of those?

[Cheese11]

I made a application.

With this application it is possible to jump to different pages (by the use of buttons).

But when I clicked on one button, the internal error appeared.

I am not using 3D graph.

Do you have any idea what there can be wrong?

[ninlmartijn]

Hello Kenny,

Thank you for your post. I'm sorry for the delay in response from NI side. I hope the following KB will give you more information. You can also create an Error log file, this will gives us the possibility to report to our R&D department for future improvements. Please don't hesitate to contact us when the problem still persists.

Best regards,

[Cheese11]

Hi everyone,

I just had the error again for a couple of times last week.

But now I got a second error when clicking the first one away.

The first and 2nd error are numbered bij 1 and 2 in the attachments.

I got no idea what can cause the error.

Maybe some of you know what the problem is now.

Regards,

Kenny

[ninlmartijn]

Dear Kenny,

please attach a log file like described earlier. The second picture doesn't look like a Labview error. Are you (by any chance) moving some block diagram objects by using the arrow keys when this happens? What were you doing when this happened?

Best regards,

[Cheese11]

Dear Martijn,

I'm wondering if it is possible to attach a log-file to a Runtime version of a program?

Because I can't come into the options menu.

I can click on Tools-->Options, but the options menu won't open.

So is it possible to build in the error log-file in the Runtime version?

It is a Runtime system, so it is not possible to move block diagram objects, so that's not the problem.

The error comes up on random.

Is it possible that it gives an error when we are using our self-made menu?

The error doesn't come up every time, but it is coming up random.

Hope you can help me some more.

Regards,

Kenny

[ninlmartijn]

Dear Kenny,

It wasn't clear that the problem was with an executable.

- does this error come up only with this exe, or are you running different exe's and are those generating these errors as well?

- on which operating system are you running? (also service pack?)

- can you try the "Specific suggestions for troubleshooting LabVIEW internal errors " options from the KB I linked earlier? Also try to update your video driver, but fist lets see if everything works better with less colors / lower resolution or the Windows VGA driver.

- can you try to run the exe on other PC's with different operating systems, how does it behave there?

Best regards,

[Cheese11]

Dear Martijn,

Sorry for my very very very late response.

I was busy with some stuff that were having a higher priority.

I'm running 3 executables, but only 1 executable generates this error.

I'm running on operating system Windows XP Professional SP3.

We have also an executable running under labview 10 on a Windows XP machine, which generates this error:

Fatal Internal Error: "drawmgr.cpp" line 3572.

I think it is about the same error like I have in Labview 8.2.1 or do I get it wrong?

I tried to all the things that were mentioned in the KB you mentioned in one of your previous posts, but still the error comes up.

I'm now waiting before the error will be generated on my system with the developement version.

Only then it's possible to send you the error logfile.

Actually, I don't want to change the colors and resolution.

Do you think that the possibility is big that this causes the error?

If you have any idea what can further cause the problem, please let me know.

Regards,

Kenny

[ben64]

I used to have these errors from time to time with LV version 8.2. I'm now running version 2009 and it never happened.

Ben64