Couldn’t re-verify as my license has expired; basically was rendering a simple file, and on frame 165 got a error saying something to the effect that Krakatoa couldn’t render the frame (I failed to write down the specific message at the time). So the steps would be as simple as…
Hey John!
I guess it happens only if rendering in sequence - I rendered 165 directly and it worked, BUT we discovered a memory leak of about 8MB per rendered frame last week, so 165*8 is about 1.3GB. If you were running on 2GB 32bit machine, chances are you have run out of memory…
I will let my machine render all frames up to 165 and see if it is going to crash… But I am running on WinXP64, so I have 4GB.
Any hardware/OS specs you could share?
Also, do you want a new license?
The next build will have a watermarked trial mode when running without a license btw…
Cheers,
Bobo
Hmm, rendering in sequence does not seem to leak memory - I guess it only happens when pressing the render button.
I am on frame 90 now, will let it go through and see what will happen around 165…
Borislav “Bobo” Petrov
Technical Director 3D VFX
Frantic Films Winnipeg
Ok, rendered past frame 165, no leaks, no crashes. I might run it at home on 32bit Windows to see how it will behave…
Cheers,
Borislav “Bobo” Petrov
Technical Director 3D VFX
Frantic Films Winnipeg
This was a 2 gig laptap, Win XP Pro 32 bit. Don’t know which build of Krakatoa.
John Stetzer
JWS
This was a 2 gig laptap, Win XP Pro 32 bit. Don’t know which build of
Krakatoa.<<
John, please try again in the latest build when you have a moment. (I’ll
privately email you an updated license so you can get back into the
software.)
Tried the file with the latest build; in this instance, rendering (just straight rendering, no saving/loading of files) ended on 166. Error message was “Krakatoa Error (title bar) bad allocation.” Last Private Byte reported in Perfmon was 579,489,792, Handle Count was 1,175, and Thread Count was 32, if that’s useful. Trying to immediately render frames 166-250 results in an AE and crash.
Tried rendering frames 166-250 after a restart; managed to get up to 201 before giving the same error on 202. Checking Task Manager this time, 1.13 gb of memory reported used.
John Stetzer
JWS
Thanks John.
I tried here on a system with less RAM than you have, and I still couldn't reproduce the crash. I'm paging to disk like crazy on this system, but was still able to (slowly) make it past your problematic frames. With 2 Gigs of physical RAM, I assume you aren't even close to paging yet.
I'll keep working with the file here to see if I see any problems pop up. Likewise, let us know if you see anything similar with other simulations.