I'm adding jobs from different projects (different video sources). I've experienced the same issue if I add only 2 jobs or 3-20 jobs. I'm typically trying to batch render jobs of around 10. So it finishes the first job, keeps the RAM full, but does not continue onto the next queue job.
I realized that there is something that has changed in my workflow (coincidentally as I started using AVP 1.5 beta2). Previously I would have all the video sources and AVP projects on my local computer. But after a recent 360 shoot at NASA Goddard, I now must use the planetarium server host all of the files. So the AVP is now rendering from/to a file server.
I just now tried a test where I copied a few video sources locally, recreated the stitch project from scratch, and submitted a batch render. The batch render was able to finish a full queue. So perhaps the potential file server conflict can help to narrow down your bug hunt.
But this problem is specific to v1.5 Beta2, since I just now tested it in v1.1 and it was able to finish a batch render via the server.
Might be related to this server issue I experienced. viewtopic.php?f=48&t=21599&p=138148#p138148
On the same note, it would be extremely helpful to have a batch render editor and queue (one that mimics APG). Part of the problem is that I have no idea exactly when a render queue is finished; how many jobs are left. I know you're in the beta stages but this is essential. I have 57 shots (900GB) with a resolution of 8000x4000px, so individually loading 10 projects to batch render and submitting the jobs is taking alot of time.
Charles Hayden Planetariumhttp://www.thefulldomeblog.com