Anyone else have ideas on how to display large images?
Thanks,
Adam
--
View this message in context:
http://www.nabble.com/Segmentation-fault-using-imshow-on-large-image-tp23207792p24152022.html
Sent from the matplotlib - users mailing list archive at Nabble.com.
-
Bugzilla from tkjacob...@gmail.com wrote:
>
> Hi
>
> It could be that you just have to much data for the stack. You can see/set
> your stack size with ulimit -s (on linux/solaris at least). Try to set it
> to
> unlimited:
> ulimit -s unlimited
>
> This has solved similar problems for me in
A 1x1 array reproduces the error:
milkyway /data/glimpseii $ gdb /usr/local/python/bin/python
GNU gdb Red Hat Linux (6.3.0.0-1.159.el4rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or d
Hi
It could be that you just have to much data for the stack. You can see/set
your stack size with ulimit -s (on linux/solaris at least). Try to set it to
unlimited:
ulimit -s unlimited
This has solved similar problems for me in the past.
Best Regards
Troels Kofoed Jacobsen
On Saturday 25 Apr
On Sat, Apr 25, 2009 at 9:53 AM, Adam Ginsburg
wrote:
> Yep, I'm running on a 64 bit machine. I've been dealing with larger
> than 4GB data files in IDL, but I'd rather use python/numpy/matplotlib
> if possible.
>
> Here's the gdb session. The error didn't happen in imshow, only when
> I specifi
Yep, I'm running on a 64 bit machine. I've been dealing with larger
than 4GB data files in IDL, but I'd rather use python/numpy/matplotlib
if possible.
Here's the gdb session. The error didn't happen in imshow, only when
I specified show(); I guess that means I must have had ioff() set
although
On my machine (32-bit Fedora 10 with 2GB RAM), it chugs along swapping
for a lng time and then fails with a Python MemoryError exception --
which is at least reasonable.
I suspect you're running on a 64-bit machine and we're running into some
sort of non-64-bit-clean issue. We try to be 64
