YOUR ACCOUNT

Home > Forums > 

Search Forums

Search results 1 - 20 of 122
First | Prev. | 1 2 3 4 5 | Next | Last 

  • Ways to Reduce Your Render Times
    ... freed) in an unpredictable order. " But FF will still only allocate a total of 1.5 GB of RAM ever, correct? Which means that the higher I set the maximum RAM usage, the less address space is available for memory fragmentation, and the earlier the Bad Alloc bug occurs. Looks like this RAM limit needs to be re-examined. 64-bit? ;) "Thanks Crapadilla, this is a much needed thread. Made it sticky." My pleasure, GMM. :D

  • Bad Allocation
    Author: JesusSheep. bad allocation

  • # XFW::Kernel::StdException>
    Author: Bionic. A fourth sent of bad allocation When going back from Filter library "distortions" to UI clicking on Filter thumbs in organic bad allocation

  • Batch renderer memory problem
    Author: GMM. Thanks for reporting. Memory allocation is the most serious issue (http://www.filterforge.com/forum/search.php?q=bad+allocation&FORUM_ID=0) with FF for now.

  • Belgium Ripple filter render size
    Author: ddaydreams. "what is the error that it gives? If it is the bad allocation error there is no solution, but if it another different one, could be possible" It's A Bad allocation error

  • Updated: Possible fix for the "Bad Allocation" error
    Author: Vladimir Golovin. We’ve just fixed a bug that may have been a cause of the infamous "Bad Allocation" error that occurs during rendering of large images. It should also improve rendering stability in general. The fix not yet available as an automatic update, so you have to download and install it manually. Here’s a Filter Forge ...

  • Thank for all the effort getting rid of Bad allocation error
    Author: ddaydreams. I can't say enough how grateful I am that I'm not seeing the Bad allocation errors anymore. Keep up the great work.

  • Help with an error.
    Author: Colorblast. bad allocation Operating system: x64 Edition (6.1 build 7601) Service Pack 1 Physical memory: 8175 MB Number of processors: 8, available: 8 Processor info: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz, ~3364 MHz Filter Forge x86-SSE2 3.006.22568.34466 ...

  • What are the differences between using FF as standalone and as plugin?
    Author: SpaceRay. "Morgantao wrote: All I can say is that with large enough images I managed to squeeze a bad allocation error from FF while in plugin mode" What do you call "large enough images" ? Is true that is possible to get a bad allocation error EVEN when using FF as a plugin but is much more difficult that this happens, at least ...

  • FF2 renders 0K files ,FF3 crashes
    ... Intel(R) Xeon(R) CPU E5462 @ 2.80GHz, ~2792 MHz Filter Forge x86-SSE2 3.003.21584.1282 Release-SSE2, August 09, 2011 09:18 [8/17/2011 10:59:34 PM Eastern Daylight Time] Exception reported at thread 0000DDFC 'RenderingMgr 09331FF8/5': bad allocation Possible original exception location: (0) : ()+0 at 007D03D4 in Filter Forge x86-SSE2.exe (0) : ()+0 at 0075CAC5 in Filter Forge x86-SSE2.exe (0) : ()+0 at 0071E5CE in Filter Forge x86-SSE2.exe (0) : ()+0 at 00A4FC81 in Filter Forge ...

  • This is the main thread for discussing the 'bad allocation' exception
    Author: Avalanche Studios. It is true that I have had the issues on large files using the standalone version using other nodes but its more of problems where it does not release data from memory and then get a bad allocation. The only time I got the plugin to crash (bad allocation) is when I used blur nodes. I think its two separate problems, I think the standalone is due to that the preview is rendering at the same time and sometimes (or always) tries to ...

  • List of open issues
    Author: SpaceRay. "Jobox wrote: 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." I agree with you and really the MOST important, interesting and useful to fix is the Bad allocation ...

  • High resolution rendering test bug report compilation inside here
    ... info: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz, ~3391 MHz Filter Forge x86-SSE2 3.006.22568.34466 Release-SSE2, November 10, 2011 15:41 [29/01/2012 17:36:01 Romance Standard Time] Exception reported at thread 00004FE8 'RenderingMgr 094C2838/0': bad allocation Possible original exception location: (0) : ()+0 at 007EB384 in Filter Forge x86-SSE2.exe (0) : ()+0 at 00773BD5 in Filter Forge x86-SSE2.exe (0) : ()+0 at 0072D5DE in Filter Forge x86-SSE2.exe (0) : ()+0 at 00A76A41 in Filter Forge ...

  • HUGE Resolutions = FAIL
    ...       E5462  @ 2.80GHz, ~2792 MHz > >Filter Forge x86-SSE2 3.001.20499.14850 Release-SSE2, April 28, 2011 13:02 [6/16/2011 9:03:08 PM Eastern Daylight Time] >Exception reported at thread 00002B2C 'RenderingMgr 0459FCA0/3': > bad allocation > >Possible original exception location: >(0) : ()+0 at 007A6514 in Filter Forge x86-SSE2.exe >(0) : ()+0 at 00736CB5 in Filter Forge x86-SSE2.exe >(0) : ()+0 at 006FB5EE in Filter Forge x86-SSE2.exe >(0) : ()+0 at 00A33A11 ...

  • 9 MONTHS with this bug and still without a fix, solution or news
    Author: SpaceRay. Please, I would like to ask if we could have any possible news about how is it going the works about fixing this bug of "bad allocation" that I think was 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 "Thanks for reporting this error. This is a known problem,...

  • RENDERING!!! :(
    Author: SpaceRay. "joBox It's BEYOND frustrating, and I've basically given up using FF unfortunately. " YES, YES; I have made the same as you, I have given up making things in FF, as I have too many Bad allocation errors, and I am fed up of loosing time and waiting to see if the render error appears or not, AND I have 16 GB RAM so it is not a problem of not having enough (I know that FF can´t use more than 1,5 GB) "I was bitching about this ...

  • Updated: Possible fix for the "Bad Allocation" error
    Author: SpaceRay. Since the last fix I have not had as much of "bad allocation" errors, BUT is also true that most of the things I have been doing are with less than 6000x5000 and when I made the 10.000x10.000 test for StevieJ I did not get the "bad allocation" error but this does not mean that does not ...

  • Gaussian blur out of memory
    Author: onyXMaster. FYI: "bad allocation" is just "out of memory". There are some circumstances where we cannot allocate more memory (running out of Windows swap space, processing large images and having a deep component tree with multiple blur-based components on one ...

  • Stable Rendering
    Author: StevieJ. Many of my filters...which aren't that complex... Some finish rendering...and some don't... Just today...I actually experienced FF corrupting the external image with a bad allocation error...no joke... sent bug report... Computer is fine...fast dual core...8 gigs RAM...Nvidia x-graphics...etc... When it does finish renders...a 12000 x 12000 finishes in about an hour... FF is the problem...and part of the ongoing ...

  • 9 MONTHS with this bug and still without a fix, solution or news
    Author: SpaceRay. I have tried to HELP the FF team making a new thread for the compilation of "Bad allocation" bug reports so they can be able to know it better, but have got no answer. High resolution rendering test bug report compilation inside here (http://filterforge.com/forum/read.php?FID=8&TID=9371) Also asked politely for more information ...

Search results 1 - 20 of 122
First | Prev. | 1 2 3 4 5 | 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,533 Posts
+31 new in 30 days!

15,348 Topics
+73 new in year!

Create an Account

Online Users Last minute:

20 unregistered users.

Recent Forum Posts:

Join our Forum Join our Forum
Over 30 000 members!
Join us on Facebook Join us on Facebook
Over 42 000 likes!
Follow us on Twitter Follow us on Twitter
Get updates quickly!
Follow us on Instagram Follow us on Instagram
Tag us #filterforge