Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!zephyr.ens.tek.com!tektronix!percy!data!kend
From: kend@data.UUCP (Ken Dickey)
Newsgroups: comp.windows.ms.programmer
Subject: Re^2: Actor specific questions
Message-ID: <466@data.UUCP>
Date: 21 Mar 91 17:46:57 GMT
References: <27106@rouge.usl.edu> <72170004@otter.hpl.hp.com>
Organization: Microcosm, Beaverton, OR
Lines: 11

adw@otter.hpl.hp.com (Dave Wells) writes:

>This seems to allow you to get into the debugger reliably. If you keep
>hitting "OK" on the debug dialog, however, ACTOR siezes up after a few more
>repaints - cause unknown.

In all cases of this type I have seen, code is (recursively) grabbing new
instances of the Windows drawing context and not giving it up.  As there
are a limited number of these (Windows resource limit), Windows dies.

-Ken Dickey					kend@data.uucp