If you load a largish image into the compositor, say 10k pixels on a side, then map it to the output and insert some other type of filtering node between the image and output, blender crashes.
This happens on a system with 16 gig of ram and nothing else running, so there should be plenty of contiguous memory available.
The bug happens with images 5k on a side, although not quite as readily.
To reproduce: Using attached blend file, insert Filter node between image and output.
CPU: i5 2500k
RAM: 16 GB
GFX: hd4550
OS: Windows 7 64
Blender: 2.63.0
Description
Description
Event Timeline
Comment Actions
Can not reproduce using 64 bit Blender on Windows 7 64bit with 8GB memory. But could easily reproduce using 32bit Blender. Are you sure you're using 64bit Blender? :)
If you're using 64bit Blender, it'll be interesting to know if testbuild2 from http://download.blender.org/release/Blender2.64/ and MSVC builds from http://builder.blender.org/download/ also crashes for you. It also could help having system-info.txt generated Help -> System Info operator.
Comment Actions
Thanks, I can verify it doesn't crash with the 64 bit versions, but does crash on the 32 bit versions.
It does seem like it should work on 32 bit versions since a 10k image should only use about 400 MB and 32 bits can address 3 or 4 gig. But knowing just to use the 64 bit version is good enough for me.
Comment Actions
Compositor works with float images, which in case of 10K input would be ~1.6GB (10K * 10K * 4 channels * <size of float which is 4 bytes>). You'll also need two images -- input and output, which would already be ~3.2GB and Windows only allows to address 3GB for 32bit applications.
So the only thing which could be improved here is give better feedback when running out of memory which is already in our TODO list (it's a bit challenging task).
Thanks for the report, but it's simply a memory limit issue :)