FF3 crashes frequently while long renders for big files

The render bar still appears after cancelling bug reporter or reporting the bug. but render never finishes(I have checked for >6 hrs). fnally i need to close the render process giving me nothing but frustrations

Details:


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

Error message

[ detailed errror report.txt ]

I got a similar message from one of you guys. Can you be more specific than that? What is causing this in a so called updated version? I've even adjusted the program settings to use more ram, use OpenGL and anti-aliasing even though my processor is pretty up there in power. Not all filters cause this but the latest one I've tried, Meshy Fun, is a disappointment because I can't render any images with it. Not good..not good at all!!

Update: I just attempted to use the same filter in the FF plugin for PS CS3. This time it rendered correctly and went all the way. Perhaps this is only a "known issue" for the standalone version of FF? Again, please elaborate on this issue and perhaps some known solutions if you can. Thank you.

Ahh, I've just twigged that the problem might be with the file size from what others have been describing. I hope the developers can fix this soon. This is a very frustrating exercise not saving an image with a filter that you really love. Thanks for the info GMM. It's appreciated.

The file I'm trying to save is:

4288 pxl x 2848 pxl (12.2 MP)
39 MB uncompressed
24bit colour.

That's really frustrating to know the resolution limit specially u recently decided to buy one genuine copy agaisnst your reward points instead of moving to get a cracked copy online



that's bad

Yes, it is unfortunate that not everyone has Photoshop or any graphics editor that accepts and works with the FF plugin. It's an expensive program to begin with and then we have this bug which is preventing such a basic function. What's the threshold of image size before the bug kicks in and kicks one out?

If PSP X4 takes 8bf plugins which are Photoshop Plugins it should work for you Colorblast. Look in the Plugin folder of your FF install folder and you should find the 8bf file, copy it and paste it into whatever plugin folder PSP X4 uses. You can use 8bf filters in PSP X4. See this webpage with the instructions to do so.

http://pspug.org/filters/filterinstall.shtml

I never had to move the plugin library for Photoshop to use the filters. It opens up the Filter Forge program when you click on the Plugin. BTW I just got PSP X4. It's a much nicer program than I remember fr om the previous versions. It reminds me a bit of Darktable, an Ubuntu based program. It works with my Raw KDC files right out of the box with no adding any additional RAW processing add-on.

To add plugin folders for Corel to use do the following

To install a plug-in from another location

1. Click Preferences in File Menu | File Locations | Plugins

2. Click Add

3. Choose the folder wh ere the plug-in is stored

The thing I am loving about PSP x4 is it uses and sees those plugins right away unlike Photoshop which requires one to copy a plugin file to a plugins folder after closing PS and then reopen PS in order to use it. Remember you should point to the Plugin Folder in your Filter Forge installation folder when adding this to your PSP x4 menu. Unlike most other 8bf plugins it requires those additional configuration files in the plugin folder to function fully.

get some info for PSP here

http://www.filterforge.com/forum/read...ssage97817

we need to buy some more softwares!!!!!

Quote
uglyboys wrote: we need to buy some more softwares!!!!!

Quote
JohnnyPC wrote: Not everybody can be gifted with or have the major dinero to pony up for more expensive software.

You can try IrfanView, it is free, though we don't officially support it.

Same here, I have PS CS5 but get the same error in stand alone or inside as a plugin... So still big issue for me either way.

uglyboys, this is not the same error. Please open new threads for different issues.

Seems like the SAME frustrating issues that they NEVER fix. It's been going on since 2.0

Known issue?? Then take it off your feature list!
http://www.filterforge.com/forum/read...8&TID=9365

I have found some interesting information and want to ask the following

GMM have said that the error comes fr om the custom memory manager and that FF is working on it, BUT is this is NOT the real source of the error ??

I have found some interesting information from oniXMaster in reference to rendering big file sizes and giving error, please see it here below

COULD THE PAGING FILE SIZE FOR TEMPORARY FILTER FORGE FILES BE THE PROBLEM ?

Quote

oniXMaster wrote: "bad allocation" means that you ran out of available memory. Please try the following: 1) ensure your paging file size isn't lim ited by a setting in Control Panel->System->Advanced->Settings(Performance)->Advanced->Change (ideally it should be System Managed and you should have enough space on disk, I recommend several tenths of gigabytes) 2) reduce the amount of memory Filter Forge uses for it's internal computations (go to Tools->Options...->Rendering and set the Maximum RAM usage slider to something like 60 instead of the default 75) Also please ensure that you have enough disk space for both paging file, you can check it in the same location as 1) ) and Filter Forge temporary files (available in the same location as 2) ). P.S. Test With 10000 x 5000 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

Quote
GMM wrote: We've reproduced the issue – this means we're much closer to isolating and fixing the bug. I'll keep you informed.

We will have to wait for FF 4.0 to see this solved or will it be available sooner on an FF 3.0 update ?

Thanks for your help

Photoshop gives me the same errors as in standalone when working on larger images, more often than not. But I'm working on images up to 7200 pixels.


Photoshop CS5 (when used as a plugin)

Win 7 / 64

8GB RAM


Hope they get it fixed very very soon...

Is curious that many times that I want to make a larger result with many filters and I mean about 2500 x 3500 not a HUGE resolution at all 70% of the times I get the "bad allocation" error using the standalone version, BUT then I use the Photoshop version and ALL is working right 98% of the times, just once got the error in Photoshop.

SO surely the standalone for me is not good to use at all. AND I said is "curious" because from other opinions and other experiences from some other users it works well for them even on standalone and with much higher resolutions.

BUT I do not care that I can´t use the standalone, If I use FF as plugin and works right nearly all the times is enough.

Quote
Morgantao wrote: The real problem is for those who are constrained to stand alone, or have problems with both ways... Hope it's fixed, for their sakes. So far I had no such problems (Touch wood)

Yes, is right, I can´t use really the standalone, BUT can use the plugin without problems (until now) but if you do not have Photoshop or any other similar host to use it as a plugin is something bad and hope that they can fix it soon.

I am glad that you do not have any problems with your FF in either way, very good for you.