From tobias.megies at web.de Sat Sep 7 17:19:09 2013 From: tobias.megies at web.de (Tobias Megies) Date: Sat, 07 Sep 2013 17:19:09 +0200 Subject: [Image-SIG] PIL build from source not finding libraries on Debian Message-ID: <522B43ED.7050403@web.de> Hi all, I just built PIL 1.1.7 from source and it was initially not finding the libraries on my 64bit Debian Wheezy (system default location!). When setting any one of the library paths (e.g. LCMS_ROOT) in setup.py to "/usr/lib/x86_64-linux-gnu/" the build finds *all* libraries as expected. See e.g. http://packages.debian.org/wheezy/i386/liblcms2-2/filelist for where the files go in Debian. I think you should consider adding these paths (/usr/lib/ARCHITECTURE/) to the default lookup paths somehow. best, Tobias From charlesc-pyimagesig at pyropus.ca Mon Sep 16 15:01:47 2013 From: charlesc-pyimagesig at pyropus.ca (Charles Cazabon) Date: Mon, 16 Sep 2013 07:01:47 -0600 Subject: [Image-SIG] PIL crashes windows 7 (blue screen) In-Reply-To: References: Message-ID: <20130916130147.GA3478@pyropus.ca> Anthony Mouraud wrote: > > Grabbing seems to work great for a while, but after some time, the process > comes to a crash. It first indicates "GRAB failed" for something like > 1-2seconds in the terminal from which I am launching my python script and > then I have a nice "blue screen" crash of my windows7. Nothing a user-space program does should be able to crash the OS kernel. 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 Software, consulting, and services available at http://pyropus.ca/ ------------------------------------------------------------------ From chris.barker at noaa.gov Tue Sep 17 01:21:23 2013 From: chris.barker at noaa.gov (Chris Barker) Date: Mon, 16 Sep 2013 16:21:23 -0700 Subject: [Image-SIG] PIL crashes windows 7 (blue screen) In-Reply-To: <20130916130147.GA3478@pyropus.ca> References: <20130916130147.GA3478@pyropus.ca> Message-ID: On Mon, Sep 16, 2013 at 6:01 AM, Charles Cazabon < charlesc-pyimagesig at 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 > Software, consulting, and services available at http://pyropus.ca/ > ------------------------------------------------------------------ > _______________________________________________ > Image-SIG maillist - Image-SIG at 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.Barker at noaa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: