Seeing this on Linux, suse 11, Nuke 6.2v1. No frameblends or holds but there are frameoffsets. The write node being output has a total of 15 nodes in the tree, 3 reads, 3 time offsets, 3 transforms 3 reformats, 2 merges and a write. There are about 20 other reads with offsets in the script, but not in the tree being written. If those are being opened too, that's probably not helping, but it's still a fraction of the number of reads in a lot of scripts around here.
We see this error a lot with frameblends, but usually the scripts are much bigger and there are a lot more reads. in that case the scripts die on open. Amount of frames wouldn't matter. This just seemed extra strange to die randomly in the middle of a render. Sorta glad its happening to others and not just here, only in that its shared misery. Systems is going to increase my file limit tomorrow, will see if it helps. I feel they shouldn't have to - the limit is there for a reason, rights? Seems like Nathan is probably correct in Nuke being lazy about destroying FileReader instances. cheers jrab > We had that with many exr type readers and timeoffsets... Removed every not > necessary reads eliminated the error. But sometimes scrubbing too much the > timeline got the error back. > Gabor > > On Sun, Nov 27, 2011 at 7:35 PM, Michael Garrett <[email protected]> > wrote: > Do you have a bunch of FrameHolds in the script? That seems to be a catalyst > for this issue popping up. > > > On 27 November 2011 09:17, ari Rubenstein <[email protected]> wrote: > I get this daily, usually when scrubbing in the viewer, or rendering a > flipbook. Or hitting the arrow keys quickly stepping thru frames. > > Quite painful and common. Seems Nuke gets 'congested' with some temporal > operations, more so then shake did in my experience. > > Ari > > Sent from my iPhone > > On Nov 27, 2011, at 12:10 PM, John RA Benson <[email protected]> > wrote: > > > Hey there - > > > > Having some strange rendering issues: Very simple script, 3 read nodes > > (exr's), just a over b for each. Except it's 4488 frames long. After a > > thousand frames or so, the render fails: > > > > OSError: [Errno 24] Too many open files: '/path/to/frames.4249.exr' > > > > I'm not sure if this is due to nuke or the wrapper and environment that > > launches the render. Seems really weird. Anyone else hit a "Too many open > > files" after rendering for awhile? > > > > thanks > > JRAB > > _______________________________________________ > > Nuke-users mailing list > > [email protected], http://forums.thefoundry.co.uk/ > > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
