LabView quits unexpectedly with DAbort 0x9B027400: Couldn't create 24 pen Error ==0

[mirode]

Hi Everybody,

I am experiencing random Labview crashes at irregular intervals between days and months. Labview just exits without any error dialog, the error is only written to LV log file (attached). There are 3 LV applications running simultainously and there is very little or no editing taking place in the meantime.The applications are a UDP server for remote controlof some devices over UDP and serial, a GUI for operating these manually (not beeing actively used when the error occurs) and a monitoring agent, checking status of a few devices over UDP and Modbus at an interval of several seconds.

This error was already reported a few years ago (here is an example) but in my case none of the solutions seem to work. Also, there were apparently no newer threads or posts regarding this issue so I wonder if anybödy still experience similiar problems with the newer LV versions.

In my case this is LV 13.0.1f2 64-bit.

Thanks in advance for any help!

[JacquesS]

Hi mirode,

have you checked the number of GDI objects, as mentioned in the last post in the discussion you mentioned?
Re: Fatal Internal Error: "drawmgr.cpp" line 3793 - Page 3 - Discussion Forums - National Instruments
https://forums.ni.com/t5/LabVIEW/Fatal-Internal-Error-quot-drawmgr-cpp-quot-line-3793/m-p/3050495#M8...

How many GDI objects do you see and is that number increasing?

Do you have the possibility do try it in a newer LV version, in order to see if the problem still occurs?

Regards,

[DesViesM]

Hi Mirode,

I have got the same problem with Labview 2015.

---

mirode a écrit :

Hi Everybody,

I am experiencing random Labview crashes at irregular intervals between days and months. Labview just exits without any error dialog, the error is only written to LV log file (attached). 

---

Did you find any solution ?

In my case, I checked the number of GDI Objects, it's around 1000, but it's far from the limit (which is basically 10 000, I tried to increased it to 15 000 but the problem still occurs).

Thanks !

[JacquesS]

Hi DesViesM,

have you also already tried the steps described in the following KB? Especially trying to reduce the number of front panel objects in order to avoid this error seems to be a good starting point:

LabVIEW GDI Object Usage Causes DAbort in image.cpp or drawmgr.cpp

http://digital.ni.com/public.nsf/allkb/ED23C965B6F2BDA586257AB5007880F7

Otherwise, if possible, I would suggest that you check if the problem still persists in LV 2016. If that is the case, you can contact National Instruments Support to help troubleshoot the problem further.

[mirode]

Hi,

Sorry for not replying in this thread earlier.

yes, I looked at the GDI objects and it is not it. Also the number of Gui objects is far less than on some of my other projects, where I experience no such behavior at all.

I think I tried the link you sent. Funny thing, since I posted the first post there were no crashes...

[DesViesM]

OK, thanks for your answers. I don't think I've got too much front panel objects because I used other VI with more of them. But I tried to reduce them still.

One more thing, I met another problem some hours before Labview crashed. First, all numerous indicators became black. Then the whole Labview screen became black, programm and project explorer (see images attached, you can also see the GDI Objects number).The labview programm was still runing normally but I couldn't see anything. After that, a Microsoft.NET error appeared but I don't know if it's linked to this problem.

Thanks in advance for your help!

[joly314]

Hi:

   Have you found the way to handle the fault (DAbort 0x9B027400), I have the same question  in my program. I tested my program for one month.I found my program quit after 40-50 houres.IT makes me so mad.Would you like to tell me how you handle it? 

 Thanks!

 Joly.chao

[wiebe@CARYA]

---

@DesViesM wrote:

After that, a Microsoft.NET error appeared but I don't know if it's linked to this problem.

---

Do you use any .NET in the VI's?

Picture controls maybe?

[wiebe@CARYA]

So GDI has a maximum object count, but there also seems to be a maximum memory. So if there are memory consuming objects (bmps?), you might run into problems much sooner.

This seems so be related: https://stackoverflow.com/questions/9723470/whats-the-upper-limit-on-gdi-objects-for-one-process-in-..., pointing to the KB184802. Not sure if it still applies in newer Windows versions.

Obviously, if something is leaking, there will be no solution. The crash time can maybe be expanded, but it will still happen. Not sure if there is a leak though...