Thorsten Scherler wrote: > > David Crossley commented on FOR-1066: > > > > Hey i saw that input modules are involved in the error trace. I wonder if > > FOR-591 and FOR-1060 are relevant. > > Need to have a look into this issues and the stack. My project will be > online next week I will need to find time to have a look.
Good. We shouldn't let such issues pass. As said in another thread, we cannot hog memory on the ASF infrastructure. > BTW the stack is not attached to the issue, right? I didn't see any need. Everyone should be running 'build test' anyway and so can directly see it for themselves. Though i suppose it might be good to have the stacktrace in Jira for future search purposes. -David > > > Dispatcher started failing on seed sample site recently with > > > out-of-memory error > > > -------------------------------------------------------------------------------- > > > > > > Key: FOR-1066 > > > URL: https://issues.apache.org/jira/browse/FOR-1066 > > > Project: Forrest > > > Issue Type: Bug > > > Components: Plugin: internal.dispatcher, seed (fresh-site), > > > zones.a.o administration > > > Affects Versions: 0.9-dev > > > Reporter: David Crossley > > > Fix For: 0.9-dev > > > > > > > > > cd $FORREST_HOME/main > > > ./build.sh test > > > > > > The first stage (the skins-based site) builds fine. > > > The second stage (the dispatcher-based site) hangs.
