On Mon, Sep 16, 2013 at 6:01 AM, Charles Cazabon < charlesc-pyimage...@pyropus.ca> wrote:
> > Grabbing seems to work great for a while, but after some time, the > process > > comes to a crash. > > Nothing a user-space program does should be able to crash the OS kernel. > quite true, but this is Windows ( ;-) ) Anyway, the video driver is a more likely culprit, but it it is PIL (or something PIL is calling), and it only crashes after a bunch of calls in one process, then a major kludge would be to run the grabbing code in a separate process with the subprocess module. IN any case, it might be useful to do to debug. Or, even simpler write a simple batch file or python script that calls another pyton script that grabs thte screen, one grab at a time in one process, but run it a hundreds or times and see what happens. -Chris > The > behaviour you're describing sounds like a resource leak of some type, > probably > in kernel-space. The most likely culprit, I think, is the driver for your > graphics hardware. > > Try upgrading your graphics drivers to the most recent WHQL-certified > version > for your hardware. > > Charles > -- > ------------------------------------------------------------------ > Charles Cazabon <charlesc-pyimage...@pyropus.ca> > Software, consulting, and services available at http://pyropus.ca/ > ------------------------------------------------------------------ > _______________________________________________ > Image-SIG maillist - Image-SIG@python.org > https://mail.python.org/mailman/listinfo/image-sig > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ Image-SIG maillist - Image-SIG@python.org https://mail.python.org/mailman/listinfo/image-sig
