jakesylvestre / cing

Automatically exported from code.google.com/p/cing
0 stars 0 forks source link

Queeny runs out of 2Gb memory for 2rqf #310

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Validate entry for NRG-CING see:
http://nmr.cmbi.ru.nl/NRG-CING/data/rq/2rqf/log_validateEntry/2rqf_2011-08-18_06
-22-07.log

What is the expected output? What do you see instead?
==> Calculating restraint information by Queeny
==> Queeny adding restraints (# elements = 164831)
Python(28372) malloc: *** mmap(size=2097152) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
ERROR: Queeny failed as per below.
Python(28372) malloc: *** mmap(size=2097152) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
CING started at : Thu Aug 18 06:51:34 2011
CING stopped at : Thu Aug 18 09:08:01 2011
CING took       : 8187.088 s

Traceback (most recent call last):
  File "/Users/jd/workspace35/cingStable/python/cing/Scripts/validateEntry.py", line 417, in <module>
    _status = main(*sys.argv[1:])
  File "/Users/jd/workspace35/cingStable/python/cing/Scripts/validateEntry.py", line 300, in main
    doWattos=doWattos, doQueeny = doQueeny, doTalos=doTalos, filterVasco = filterVasco ):
  File "/Users/jd/workspace35/cingStable/python/cing/core/classes.py", line 1152, in validate
    validateFastest = validateFastest, validateCingOnly = validateCingOnly, validateImageLess = validateImageLess)
  File "/Users/jd/workspace35/cingStable/python/cing/core/validate.py", line 132, in validate
    project.runQueeny()
  File "/Users/jd/workspace35/cingStable/python/cing/PluginCode/queeny.py", line 586, in runQueeny
    nTtracebackError()
  File "/Users/jd/workspace35/cingStable/python/cing/Libs/NTutils2.py", line 141, in nTtracebackError
    traceBackString = format_exc()
MemoryError

Original issue reported on code.google.com by jurge...@gmail.com on 7 Oct 2011 at 12:03

GoogleCodeExporter commented 8 years ago
No time to fix anytime soon.

Original comment by jurge...@gmail.com on 27 Feb 2012 at 9:10