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

Use FF in plugin mode.
Load your image (or create a new image) in photoshop and open FF from the filters menu.

As you can see in all this threads about this SAME ERROR it comes already SINCE 6th SEPTEMBER 2011 !!!

AND since 9 MONTHS AGO that this bug has been reported the ONLY answer that comes from the developer team is

Quote
Thanks for reporting this error. This is a known problem, the developers are working on it. Hopefully it will be fixed in the nearest future.

In 3 months more (and this will happen as I do not think this will be fixed before) we will be able to celebrate the first year of life of this bug and make Bug Birthday celebration

Please for more information about this I suggest to read also the threads here below.

Here of all the threads related to this error

SEPT 2011 # XFW::Kernel::StdException>

Please, MORE information class XFW:Kernel:StdException> bad allocation

HUGE Resolutions = FAIL

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

FF3 crashes frequently while long renders for big files

Help with an error (bad allocation)

I think that if the problem is related to the custom memory manager inside Filter Forge, I do not see any kind of fix other that rebuilding or modify this custom memory manager, BUT perhaps this will not be possible until FF 4.0 probably.

i believe this is the memory allocation bug and spaceray is saying this is unfixable. i dont recall ever seeing that. i do know FF, inc. hasnt found a fix yet, but i've never heard them say it was unfixable.

what little i know of this is that i get it, too and it happens when the 2 gigs of memory that filter forge allocates from windows gets used up. windows and filter forge then seem to get into a fight and windows always wins and filter forge either crashes, locks up, or gives multiple error messages and reluctantly carries on. i suspect this may be a library (.dll) problem, but i'm not a programmer so that's mostly just a wild guess.

part of the problem of all this is that filter forge is 32 bit, which means it cant address more than about 2 gigs. if they went to 64 bit, which a lot of us would love, it's likely this allocation bug would go away, though that's not a given either.

about all you can do for now is cut your file size down or find ways to keep FF from maxxing out its memory allocation. sometimes when i hit this bug, if i close FF and restart it, i can get it to work on that same file... for a while. but, it's a very common bug and one which i hope gets addressed sometime soon.

Quote
Kraellin wrote: i believe this is the memory allocation bug and spaceray is saying this is unfixable. i dont recall ever seeing that. i do know FF, inc. hasnt found a fix yet, but i've never heard them say it was unfixable.

If you read right I have NOT said that is unfixable, and is true that there is NO news that this is not possible to fix, AND I have about 8 emails sent by the FF support team that say that they are working on it.

What I said is that most possible can´t be fixed if they do not change or modify the custom memory manager, and the FF team have said that this was very difficult to do and would need a whole rebuild of the system and would take much work to do it.

I have already sent about many FF bug reports to the FF team explaining what happens when I get this error and so they can know when and why this happens and can reproduce it better, although always the answer has been that this is a known issue and they already know about this.

Kraellin you have said it this yourself as you have not used the QUOTES

Sorry, you are right, is true that in the FIRST post I did say that this bug can´t be fixed, my fault that I did not remember and see it, but this was a like a way to force FF team to SAY SOMETHING as this was on a Thursday and this could be seen from GMM and could perhaps tell the FF team ad have any possible answer telling me that I was wrong and it COULD be fixed. I must learn that this way does not work and FF did not care about this.

Quote
Morgantao wrote: I don't recall seeing an official "no can do" on fixing this, it's just that they haven't figured out how to do it yet.

Yes, there is no official news about it, well there is NO news, about it only that is a KNOWN issue and they are working on it, that´s all.

Quote
Stepunk wrote: I receive the same error... so I bought a piece of software that I cannot use? that's great...

I am making some testings that could show that this is not true, and you CAN use the software WITHOUT this bug ONLY if you use Filter Forge with Photoshop or possibly any other host that makes Filter Forge being used as plugin and not in standalone mode.

I will put more news about this later when I finish my testings and could have A GOOD NEWS to tell.

It was joke

I know already very well that in ALL the browser I have tried the QUOTES does NOT WORK anymore and are broken and yu are forced to copy by hand the text, and then add the name and the quotes and simulate that it was copied by the forum

I also have put a thread about IE not supporting .ffxml files

Was is important here is that You were right that I did say that it could not be fixed

I think i have solution of this.

Im talking right now with Filter Forge 4 Professional. I'm not sure for earlier versions.

This problem was reproduced in my case due installing the backup of filters (yeah the whole backup of all filters in library)

SO! All i did this and the error were reproduced.

What I did was to go to %Appdata% / Roaming / Filterforge 4

Erase all the xml in the folder of filter forge.

enter / System / folder.

erase all .xml and version files (no folders, just Xmls

again try to execute your Filter forge (Did on standalone and work fine)


So i believe this bad allocation error happens cause the cache of batches and thumbnails is not correct cause you either apply something or it becomes corrupted. I'm talking about my case, however i cant confirm on someone else case, so I hope this helps.