[ADMB Users] memory allocation error

Fowler, Mark Mark.Fowler at dfo-mpo.gc.ca
Tue Aug 13 05:52:21 PDT 2013


Attempting to run a (monstrous) model on a new machine with the latest
ADMB, I get a memory allocation error right off the bat, no churning.
This model runs on an XP machine with 4 GB RAM, whereas the new Windows
7 machine has 32 GB (paging file is 16x that of the XP machine), so
available memory can't exactly be the problem. Is there a difference in
the latest ADMB that accounts for this? Does the move from a 32-bit to
64-bit machine confound something? I notice that the System-Performance
Options-Advanced has changed between OS's. Both allow Processor
scheduling and Virtual memory adjustments, but only XP has a separate
Memory usage (Programs vs System cache). On both machines I opt for
Programs, but don't know how the Windows 7 machine resolves the absent
Memory usage block. The no-longer-working program was a Borland compile
with the following memory settings:

 

  arrmblsize=90000000;

gradient_structure::set_GRADSTACK_BUFFER_SIZE(2500000);

gradient_structure::set_CMPDIF_BUFFER_SIZE(200000000);

gradient_structure::set_MAX_NVAR_OFFSET(2500);

 

I also compiled a mingw version on the new system with the latest ADMB
(problems reported in earlier email were due to incompatible Borland
include files - resolved), and get the same response, immediate memory
allocation error with no churning.

 

Anyone know why it no longer obtains the needed memory?

 

Mark Fowler 
Population Ecology Division 
Bedford Inst of Oceanography 
Dept Fisheries & Oceans 
Dartmouth NS Canada 
B2Y 4A2 
Tel. (902) 426-3529 
Fax (902) 426-9710 
Email Mark.Fowler at dfo-mpo.gc.ca <mailto:Mark.Fowler at dfo-mpo.gc.ca>  



 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.admb-project.org/pipermail/users/attachments/20130813/3524ffbb/attachment.html>


More information about the Users mailing list