YOUR ACCOUNT

Search results 61 - 80 of 122
First | Prev. | 2 3 4 5 6 | Next | Last 

  • # XFW::Kernel::StdException>
    Author: Bionic. a sixth sent of bad allocation when going back from previous crash @filter library distortions" to UI clicking edit filter. I'll now pause submitting XFW::Kernel::StdException Unless you want more or I'll stumble upon elsewhere

  • Error when saving a 10,000 x 5,000 render
    Author: Morgantao. 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 ...

  • Updated: Possible fix for the "Bad Allocation" error
    Author: Vladimir Golovin. We've updated the fixed installer (the download link is the same, see the first post of the thread). It now includes several improvements that reduce memory fragmentation, which, we believe, is the primary cause of the Bad Allocation error. Please give it a try and report the results here.

  • # XFW::Kernel::StdException>
    Author: Bionic. yes i could.. when clicked misc in filter library this occured again bad allocation I could not submit report hence buttons greyed out? (attached screenshot) But I found ~tmp file, will see if it's usable It seem different than this report

  • Shar´s Forge
    Author: Sharandra. Hmm, I can´t submit it, as it is, it´s too slow. It renders fine at 2000x2000, takes 5 minutes. But at 4000x4000 it first gave me the bad alloc bug, then I turned down memory usage. Now, after a few hours it´s only at around 25% :S

  • Where does the FF plugin go in PS elements?
    Author: Sharandra. My mom just got herself PS elements because of the bad allocation error. I´m trying to help her install it, but throwing it into the Plugins folder apparently didn´t work. So where should it go?

  • HOW MUCH important is the Page File size AND where should be located?
    ... problem for the life of the SDD drive. All the applications I have does not care that the page file is in E: instead of C:, and I do not get any error from other application in reference to memory problems. The only apllication I have a "bad allocation" error problem is in Filter Forge 3.06 Pro From the text below from onyXMAster I wonder HOW Filter Forge works with the Page File and the temporary files "oniXMaster wrote: "bad allocation" means that you ran out ...

  • Ways to Reduce Your Render Times
    ... would then be used less the temporary folder? 6 - I think that Using the Teporary folder on SSD Hard drive would be better than using a normal Hard Drive, as it would be faster. "Vladimir Golovin wrote: In light of the recent hunt for the Bad Alloc bug, this is a bit complicated. Setting the RAM usage slider to the max (90%) minimizes cache churn but leaves little room for memory fragmentation. Conversely, keeping in the middle (50-60% or so) increases the cache churn but leaves more room ...

  • Rendering above 5000x ???
    Author: SpaceRay. StevieJ as you can see in this other thread made by Sharandra with the FF 4.0 Beta 1, regretably it has NOT been solved yet. Bad allocation error go away! (http://filterforge.com/forum/read.php?FID=17&TID=10449) As seen also in this thread "GMM We're working on it!"

  • FF3: Slow
    Author: Morgantao. In the last 5 posts or so there are the same issues reported for pretty much ever... Memory usage of 1.5GB max, while the system has 6 or 8 or 12 GB. Slowness with relativly small images. FF going belly up with "bad allocation error" all the time.... For crying out loud, FF inc, DO SOMETHING!!!!

  • FF3 crashes frequently while long renders for big files
    Author: saurabhgayali. 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: bad allocation Error message

  • Updated: Possible fix for the "Bad Allocation" error
    Author: ThreeDee. I am using FF 3.014 and I get the "Bad Allocation" error on a 10000x10000 image. I can resolve it for the rendering stage by turning off progressive previews, but then it reappears and crashes FF on trying to save the image. On testing further, it crashes on save if I have an input ...

  • Exception error after installing Filter Forge Backup and Librarian
    Author: Kev914. I'm having the same issue. After copying the backup Librarian files into the Filter Forge roaming filter, I get this error when I try to start Filter Forge bad allocation I submitted the bug reports. I also tried re-installing Filter Forge but still get the same error. I also purchased the Librarian, but I never received a download link.

  • List of open issues
    Author: joBox. So out of the 9 ongoing bugs listed above, only 2 have been resolved? The ONLY one I'm interested in is the Bad Allocation bug that has been going on since V2. I would like to actually RENDER a large image (as advertised) without it crapping out 50% of the time. So will this be fixed in V4? I don't expect an answer, but I am assuming yes.

  • List of open issues
    Author: Morgantao. I sure do hope the Bad Allocation bug is solved in FF4. That alone would be a good reason to upgrade. The only thing is... It's a bug. Bug fixes are supposed to be free. So if they manage to solve the bug for FF4, they should upload a fix for FF2 and FF3 as well. Unless ...

  • What are the differences between using FF as standalone and as plugin?
    Author: SpaceRay. As now the only good way to use Filter Forge is as a Plugin and not as a standalone to be able to avoid the bad and unwanted "Bad Allocation" bug (at least in Windows) I want to bring this thread up again for anyone that want to know the difference. Anyone that knows or want to add more advantages, comments or anything that could be useful to this thread is free to do it ...

  • List of open issues
    ... SpaceRay. "Morgantao wrote: I certainly hope not. " Perhaps you may be possibly wrong IF the fix involves making a new software and much changes to be able to make it to work right. Why would they take more than 9 months to fix the "bad allocation" bug ? BUT you may be right that small bugs of some of the above ones could really be available as a FF 3.0 update and not need to wait for 4.0

  • Updated: Possible fix for the "Bad Allocation" error
    Author: SpaceRay. I have just downloaded the newest upd ate and will test it more and see if I still get the "Bad allocation" or not. In the first two tests, one with a 6000 x 6000 image it did WORK without any problem, I have to say that before this was not possible :ff: AND much more important with a 14500 x 8500 image and the Dropshards filter when ...

  • FF4 crashes on getting filter list
    Author: Ken1171. I am having the exact same problem, but only after installing Filter Library Backup 4.0. I get this error message: " bad allocation" I have 16GB RAM, and still had over half of that reported as free when the program crashes with the error message above. I am also running Windows 10 x64 with all updates installed. I have tried running the program with Admin credentials,...

  • High resolution rendering test bug report compilation inside here
    Author: SpaceRay. I wanted to help FF solve in a better way this problem and have sent them many bug reports and wanted that others could also help but seems that nobody have posted any help here and I wonder if they have at least sent bug reports of the bad allocation error to the FF team so they could have more information and know how many persons are having this problem and are interested to solve it.

Search results 61 - 80 of 122
First | Prev. | 2 3 4 5 6 | Next | Last 

Join Our Community!

Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!

33,712 Registered Users
+19 new in 30 days!

153,534 Posts
+31 new in 30 days!

15,348 Topics
+72 new in year!

Create an Account

Online Users Last minute:

24 unregistered users.