YOUR ACCOUNT

CeleriedAway
Posts: 26
Filters: 1
Hello FF team.

Today I tried to use batch renderer, works well but it has some memory issue.
I'm rendering 300 tasks now and every task uses its own external source image. It's actually a frame sequence.
Several hours have passed and memory consumption is alreay 1.3GB
but only 100 frames rendered so far. Forge is a 32bit application and I strongly feel std::bad_alloc is already looking over my shoulder. ))

It seems renderer does not deallocate loaded image after task is done. Previous versions of FF have this issue too.
I don't think too much people have this problem ))), but this will be greate to be fixed. )
  Details E-Mail
CeleriedAway
Posts: 26
Filters: 1
Yahoooo!!!
Exception caught at thread 000018C8 'Application':
<class XFW::Kernel::StdException> bad allocation

229 frames was finished. smile:)
  Details E-Mail
GMM
Moderator
Filter Forge, Inc
Posts: 3491
Thanks for reporting. Memory allocation is the most serious issue with FF for now.
  Details E-Mail

Join Our Community!

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

33,711 Registered Users
+18 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:

23 unregistered users.