DAbort 0xF89E2EC9 in drawmgr.cpp

[Jed_Davidow]

I wrote a test program in LV that calls a thrid party device (PCI Connected).  After my system loops for several days, we get this error:

DAbort 0xF89E2EC9 in drawmgr.cpp

Any help would be appreciated.  First thing being, can we determine from this that this is solely a LV error?

LV 2011 SP1 with f1 patch. (11.0.1f1) on Windows 7 x32 (PXI System image 1.2.1f6)

[Joel-I]

Hi Jed_Davidow,

Take a look at this Knowledge Base article and try out the steps described:

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

Let me know if that works.

Regards,

[Jed_Davidow]

I saw that one, but I don't think it's pertinent...

1) I am not running this as an EXE (yet).

2) The error happens after several days of running in a loop; so slowing down the load times of individual components won't help.

3) The article claims this was fixed in LV7+, and this is 2011 SP1; (I also saw an article claiming that this was an internal error fixed for 2011 SP1).

I have rev'd the code to 2012 SP1, I'll see if that fixes it.  The problem, again, is that I need to run continuously for several days to make it error, and that makes debugging almost impossible.

[Joel-I]

Hi Jed_Davidow,

Let me know what occurs with LabVIEW 2012 SP1.

Also, make sure that you use the latest patch for LabVIEW 2011 (f2):

http://www.ni.com/download/labview-development-system-2011/2657/en/

Also, try updating your hardware drivers as described in this Knowledge Base article:

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

Regards,

[MarredCheese]

I got this same error (in Labview 14.0 32-bit on Windows 7) and wanted to mention the cause/solution in case it helps somebody down the road, even though it's probably a pretty obscure scenario.  I actually got various numbers in the error message, but it always took the form of "DAbort # in drawmgr.cpp."

In my case, the error was due to my code setting the system tray icon and tip strip 10 times per second.  My program would run for a minute or two at most before crashing.  I changed the code to only update the icon/tip when necessary (based on infrequent events), and the problem went away.  The code I'm talking about that sets the icon/tip is here: https://lavag.org/topic/14060-put-your-labview-in-the-tray-once-and-for-all/