| CeleriedAway |
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. ) |
|
| Posted: December 9, 2012 6:50 am | ||
| CeleriedAway |
Yahoooo!!!
Exception caught at thread 000018C8 'Application': <class XFW::Kernel::StdException> bad allocation 229 frames was finished. |
|
| Posted: December 9, 2012 1:07 pm | ||
|
GMM
Moderator
Posts: 3495 |
Thanks for reporting. Memory allocation is the most serious issue with FF for now.
|
|
| Posted: December 10, 2012 3:38 am | ||
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,738 Registered Users
+6 new in 7 days!
153,584 Posts
+6 new in 7 days!
15,355 Topics
+5 new in 30 days!
Arrow, 8 unregistered users.