My LabView 2011 application crash every hour with drawmgr.cpp error.

[Boss Techno]

This is an application develop in LabView 2011 F2, in and industrial application . The application is not compile and still run in normal mode. Every hour, i received a Crash windows with the "drawmgr.cpp" error code.  

I did try to update my LAbview, Update video Card, Update resolution and color

I did change computer and try on windows XP and windows 7 

Always the same crash after 1 hour.  

Does any one have and idea to solve this issue

[smercurio_fc]

This error has been reported before, and was supposedly fixed in 2011 SP1. You indicated you had f2, not SP1.  However, at least one person indicated that the problem still existed with SP1. Still, the trigger for the crash seems to be varied, at least based on the postings I've seen. In one case it was caused by a person having a custom icon in the toolbar (not clear what he meant by that - he might have been referring to a custom VI icon). In another post it was caused by a background picture on the front panel. I would suggest searching this forum for "dabort" and looking over the threads. You may need to contact NI tech support directly.

[Boss Techno]

I did upgrade LAbview to SP1 + patch for SP1.

I restart the application and after 1 hour again : "Dabort 0x9B027400 in Drawmgr.cpp  VErsion 11.0.1f1". The upgrade did fix this Bug

Any Idea ???

[altenbach]

Is it reproducibly after exactly 60 minutes or does the time vary somewhat?   What does the program do? Is there any timed state transition or timeout?

[Boss Techno]

It is basicly a front panel with pushbutton and indicator using and area for showing different Sub Vi  as selected from front panel.  This application is basicly sending and receiving information from/to  a Umac  (Delta-tau)  with and ethernet communication and  Delta-tau vi librairy.

Basicly the front panel is always present  plus  one sub Vi on right side for indication. No one is touching it for many hours after the system is setup and running.

the LVLog. txt is showing :  "DAbort 0x9B027400: Couldn't create 24 pen Error ==0
c:\builds\penguin\labview\components\LVManager\trunk\11.0\source\drawmgr.cpp(4515) : DAbort: Couldn't create 24 pen Error ==0"

I have one SUbVi including Graph but the crash append even is this SubVI is not showed.

This is driving me Nut's

[altenbach]

Sorry, I am still confused! 😮

Is it a real crash requiring a LabVIEW restart or is it just the apperance of an error message?

---

@Boss Techno wrote:

No one is touching it for many hours after the system is setup and running.

---

Obviously, if it is crashing after 60 minutes, it cannot be running for hours. You say there is network communication. Could it be a connection timeout?

Does the delta-tau library use any custom dlls as far as you know?

[Boss Techno]

Real Crash,  I need to go to task manager to close LabView.

But each time a restart the aplication it will run for approximatly 1 hour each time.

Delta-TAu have there own VI librairy for many years.

Regarding commuication Time Out, I will be supprise because While the Labview is frozen, I can start and other program  that can easily communicate with the UMAC

[Joel-P]

Hello Boss Techno,

Has this specific application every worked, or is this the initial release?

The specific error you mentioned appears to be an issue when creating/modifying images for the front panel, if you could try reducing or disabling any advanced artwork/graphics on this application it may help reduce the chance of this error.

This error was also caused in earlier releases by moving high data images on controls with arrow keys.

Here are some documents I found while trying to get up to speed on this issue, and I will continue to research what may be causing your error.

Drawmgr.cpp, Line 2931 Error When Running a LabVIEW Executable: (LabVIEW 6.1)

http://digital.ni.com/public.nsf/allkb/16CF1334D094A4F6C1256BE30074B9FE

"error drawmgr.cpp line 2923" from another LabVIEW user: (LabVIEW 2010

http://forums.ni.com/t5/LabVIEW/error-drawmgr-cpp-line-2923/m-p/1978571

General LabVIEW internal error help procedure:

http://digital.ni.com/public.nsf/allkb/01B186B5CEB1D07786256747000F4319?OpenDocument

Thanks,

~jp

[Boss Techno]

I did find what is causing the Crash in my VI.

We were using a connection to a database for retrieving information into a global database. The program require and Opening, a query, and a closing of the connection to the database. This small program was located into a While loop executing every 300ms for fast refresh.

After I remove this small program of my global while loop the application simply stop crashing. I did spent many hours of testing before getting this result. I did change my program by using some Global Variable coming from another VI to solve the issue.

Those small VI are part of the Database connectivity Tool Kit.

So now you know what is creating this failure.

Thank you for your help

Best Regards

[altenbach]

It is good you were able to fix it.

(It is not sufficient to simply remove code that causes problems, we also want to know the exact reason why it crashed)

Do you think there is a bug in one of the toolkits? If so, did you report it?

Was there a resource leak caused by constantly opening and closing the connection?

I don't understand your solution ("using some Global Variable coming from another VI").