drawmgr.cpp at line 3386 error

[Matthias Waschk]

Hello togehter,

i have to talk to an USB device via an sub vi that uses ActiveX calls. This
routine works fine. So far so good. To check if the routine and the hardware
(a meM PIO USB) are running well, i run them in an loop over and over again.
After 1100 loops (+- a few, i have tried it many times) LabView hangs up
with this "drawmgr.cpp at line 3386" error. In this case the knowledge base
isn't a great help. This error happens on differend pc's, differend
resolutions, differend colordepth.... The update to LV6.0.2. does not help
too....

What is the problem????

--
MfG / best regards
M.Waschk mailto:m.waschk@t-online.de

[Mark A. Hanning-Lee]

M.Waschk wrote:
>
> Hello togehter,
>
> i have to talk to an USB device via an sub vi that uses ActiveX calls. This
> routine works fine. So far so good. To check if the routine and the hardware
> (a meM PIO USB) are running well, i run them in an loop over and over again.
> After 1100 loops (+- a few, i have tried it many times) LabView hangs up
> with this "drawmgr.cpp at line 3386" error. In this case the knowledge base
> isn't a great help. This error happens on differend pc's, differend
> resolutions, differend colordepth.... The update to LV6.0.2. does not help
> too....

Have you tried www.ni.com/failure ?
That is distinct from the knowledge base.

Mark

[M.Waschk]

Hello together....


> Have you tried www.ni.com/failure ?


Yes i do...

No a great help....

Greetings

M.Waschk

[JonM]

Hmmm,
I thought this kind of error had been fixed in LV 6? I'm not familiar with LabView 6, but in 5.1 if you try and load bitmaps or jpegs on to the screen (or if the front panel of the VI has an image on it) it causes errors in drawmgr.c. Does your VI contain any kind of graphics, pictures, images, decorations, etc? If so, try removing them (if possible). I admit this isn't ideal, and may not be related to your problem, but it's the only way I've ever got rid of drawmgr errors.

If this doesn't help, try using Windows NT task manager to keep track on the allocated memory and number of allocated handles. You may have a memory leak, or your ActiveX control may not be releasing handles.

Hope this is of some help,
Jonathan

[Matthias Waschk]

Hi all,

my program was made like this: loop > open aktivex > do something > close
activex > loop end,
so activex was opened and closed over and over again...

I thing that maybe a stack or something was running over ( at about 1000
loops ) and cause the program to crash!

Now i do it like that: open activex > loop > do something > loop > close
activex,
this is running very fine.

thanx...any way...

[Zvezdana S.]

Matthias,

These crashes (drawmgr.cpp) usually result from video driver problems...since LabVIEW is a completely graphical environment, it demands more from a video card than most other Windows programs. You should contact the manufacturer of your video card to make sure you are running the latest version of your video driver. If you are, and you still get the crashes, you should change your video adapter to the standard Microsoft VGA adapter...this will most probably stop the crashes. If it does, then you may want to consider getting a higher-performance video card.
In Win2000 it is a bit harder (then in Win98) to choose a standard VGA driver.
I found this link on the Microsoft support site that describes how to set up the standard VGA driver:

http://
support.microsoft.com/support/kb/articles/Q268/8/52.ASP?LN=EN-US&SD=gn& FR=0&qry=standard%20VGA%20adapter&rnk=2& src=DHCS_MSPSS_gn_SRCH&SPR=WIN2000

I hope these suggestions help. Please let us know if you have any other questions. Have a pleasant day.

Sincerely,
Zvezdana S.
National Instruments