If its really because you are running out of memory then the OOM killer will send a SIGTERM, do you see that in strace?
The doc builder respects the usual SAGE_NUM_THREADS environment variable. On Wednesday, May 28, 2014 11:27:41 PM UTC+1, Dima Pasechnik wrote: > > On 2014-05-28, Dima Pasechnik <dim...@gmail.com <javascript:>> wrote: > > On 2014-05-28, Volker Braun <vbrau...@gmail.com <javascript:>> wrote: > >> This is multiprocessing.pool waiting for children to finish. > > To finish, or to start? > > > >> The question is what happened to the children. > > They are seemingly alive, but don't do anything at all, according to > > dtruss. > > > > > > The main process occupies over 100Mb of RAM, which is kind of a > > lot for a process that builds docs... Its children don't occupy much. > > > > Perhaps the children wait for memory to become available, or something > > like this. > > I also tried building pdf docs, and the result is very similar: > a master docbuild process waiting for a slave (in this case, just one) > to do something, and the slave doing nothing at all. > Using sage's python (running docbuild from Sage's shell) > rather than system's python does not change the > picture either. > Hitting ctrl-C in this case results in something remotely meaningful: > > ... > [history_a] loading cross citations... looking for now-outdated > files... none found > [history_a] no targets are out of date. > ^CProcess PoolWorker-63: > Traceback (most recent call last): > File "/usr/local/src/sage/mav/sage/src/doc/common/builder.py", line 1477, > in <module> > Traceback (most recent call last): > File > "/usr/local/src/sage/mav/sage/local/lib/python/multiprocessing/process.py", > line 258, in _bootstrap > getattr(get_builder(name), type)() > File "/usr/local/src/sage/mav/sage/src/doc/common/builder.py", > line 276, in _wrapper getattr(get_builder(document), 'inventory')(*args, > **kwds) > File "/usr/local/src/sage/mav/sage/src/doc/common/builder.py", > line 487, in _wrapper self.run() > File > "/usr/local/src/sage/mav/sage/local/lib/python/multiprocessing/process.py", > line 114, in run self._target(*self._args, **self._kwargs) > File > "/usr/local/src/sage/mav/sage/local/lib/python/multiprocessing/pool.py", > line 102, in worker x.get(99999) > File > "/usr/local/src/sage/mav/sage/local/lib/python/multiprocessing/pool.py", > line 548, in get self.wait(timeout) > File > "/usr/local/src/sage/mav/sage/local/lib/python/multiprocessing/pool.py", > line 543, in wait task = get() > File > "/usr/local/src/sage/mav/sage/local/lib/python/multiprocessing/queues.py", > line 376, in get self._cond.wait(timeout) > File "/usr/local/src/sage/mav/sage/local/lib/python/threading.py", > line 358, in wait _sleep(delay) > File "c_lib.pyx", line 176, in sage.ext.c_lib.sage_python_check_interrupt > (sage/ext/c_lib.c:1696) return recv() > File "c_lib.pyx", line 176, in sage.ext.c_lib.sage_python_check_interrupt > (sage/ext/c_lib.c:1696) File "c_lib.pyx", line 73, in > sage.ext.c_lib.sig_raise_exception > (sage/ext/c_lib.c:872) KeyboardInterrupt > File "c_lib.pyx", line 73, in sage.ext.c_lib.sig_raise_exception > (sage/ext/c_lib.c:872) > KeyboardInterrupt (sage-sh) > > Is there a (hidden?) option or an easily tweakable parameter in a > config file to turn the multiprocessing of docbuild off? > > Thanks, > Dima > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
