The test should not use up more then a few megabytes of RAM. Even on very
large datasets you should never really use more that 1 or 2 gig of RAM
perl MAKER instance
It's possible that their may be other perl modules that are broken need to
be reinstalled on your system. This can happen when perl gets updated,
but you are pointing to modules built for a different perl version with
the PERL5LIB environmental variable. Make sure you you have the latest
version of MAKER and run with --debug set. Collect that output and send
it to me (the --debug option does some dependancy checking).
I know there is an issue on Macs with updating perl's DB_File module that
causes it to gobble up big sections of the hard drive (it will eventually
fill the drive if you let it). It's not a memory issue but just one
example of how broken modules can cause weird behavior.
>When I try to run the test provided with maker2, maker start to use a
>huge amount of memory. I stoped it after it reach ~100go of memory
>used. I believe the test should not use that amount of memory.
>In an other message someone suggest that the bioperl version installed
>could be the cause of the problem, but the bioperl installed on my
>cluster is already at version 1.6.
>perl -MBio::Root::Version -e 'print $Bio::Root::Version::VERSION,"\n"'
>Unfortunately I don't have an error message to provide, that could
>clarify my problem.
>But maybe it is a recurrent problem and you know a few things I should
>maker-devel mailing list
>[hidden email] >http://box290.bluehost.com/mailman/listinfo/maker-devel_yandell-lab.org