Error when saving a 10,000 x 5,000 render

Hi There

Last night I rendered a 10000 x 5000 image of this filter (one of my favourites)

Kromatism



When I went to save it as a .JPG, this error occured :

<class XFW::Kernel::StdException> bad allocation

After cancelling the error, saving halted, but the save progress dialogue box remained open - after cancelling that, I got this error :

Object <class XFW::IO::File>@0804F6F0 was not released before destruction.

FF does save a partial JPG file which can be opened, but obviously all the image data is not there - also, attempting to save in other file formats gets the same results.

The error doesn't seem to be fatal, as FF remains open, usable and stable

I then re-booted my machine, rendered again and attempted to save again, the same thing happened

I tried with a few other large sizes, i.e. 4000 x 4000, 5000 x 5000, the same thing happened

But, I must say - the render executed perfectly, using all cores available - in fact the very first attempt was at 20,0000 x 10,0000 which rendered on my machine in 17 minutes, only to be lost on saving, which I can assure you was very annoying

Other filters seem fine at hi-res, I rendered Alien Ribs at 20,000 x 10,000 in 4 minutes and it saved without a hitch.

Admittedly, I am running the trial, of which I only have a few days left, so would be grateful if you could tell me why this is happening with this filter and possibly cure the issue ?

Thanks very much for your time

Best

J

P.S. I will check if there's a specific problem with this filter and such image sizes with properly set up paging file. The fact that other filters render fine makes me think that you're running out of disk space (there are two bitmap-based components in there, with such resolutions the temporary files alone might take from 3 to 6 gigabytes )

onyXMaster thanks for your prompt response and help

Following your instructions, I was able to render a 20Kx10K (20000 x 10000) image, which I intend to post on the forum - that was my intention from the start, I haven't seen any posts relating to large format images, so thought this might be cool

Going back to the original problem, it seems that page filing was turned OFF for some reason, I had recently installed Vista SP1 - maybe that has some bearing on it, anyway - turning it on did the trick and reducing FF's RAM usage (as you correctly suggested) to 45% also must have worked

Again, thanks very much for your help

Best

J

Quote
Biomechanic wrote: But, I must say - the render executed perfectly, using all cores available - in fact the very first attempt was at 20,0000 x 10,0000 which rendered on my machine in 17 minutes,

Nice to hear that

Bad allocation in most program relates to memory allocation.

Think of computer memory as a giant library with lots of shelves.
The RAM is the small shelves right next to the librarian. It doesn't take the librarian much time to access these books.
But there's no way to fit a whole library in just those shelves, so you have the Page File, which is a set of very long shelves located somewhere else. Those shelves have much more storage space, but it takes a while for the librarian to come get the books fr om here.
Not only that, to get you these books, he needs to take the books off the near shelves (RAM) and put them in the far shelves (Page File), to make room for the books you want in the near shelves.
Now imagine you don't have enough space in the Page File. Wh ere will the librarian put the books? He can try to jam them between other books, but that will get the pages all wrinkled, and some of the books will fall on the floor or get lost behind other books.... A whole lot of mess...
That's when you get errors - The librarian can't find the books you're looking for, and get mad at you for asking them, but the librarian can't shout at you for interupting his work and asking him for books he can't find, because it's a library, and you need to keep quiet. That only gets the librarian more angry, and the pressure builds up untill he decides to burn all the books on the subject you asked for. Then the librarian gets taken to the mental hospital because he's had a mental breakdown.
Now all is lost and you have to start your research all over again, hoping the new librarian won't lose his mind, but unless he's got more room in the library, it's likely it will all happen all over again.

OK, so I got a little carried away

Obviously the librarian is senile, or he has Alzheimer's desease, and untill the doctors can find a cure, the librarian is going to missplace books, and go mental.
Thank god it's a librarian and not a postal worker

I can't seem to reproduce the error...
Using the standalonen version I let my copmuter choke on 12MP (and higher) images, using this and other filters.
While my computer totaly froze for periods of 12 minutes at a time (mouse was choppy, numlock took a while to turn on/off), it still produced the results with no errors.
I can even tell you I haven't reboot the computer in a few days, and I have around 15 IE windows open for all that time, Chrome windows open for all that time.
In fact, every other thing I do in IE causes it to crash and reloard the page... But FF did the job.