Dear Tyler,
What you describe seems very hard to reproduce and debug. I doubt we can really help much if nobody else can reproduce it.
Just a gut feeling tells me that it could be something specific to your machine / OS combination, e.g. not enough memory, or corrupted packages, etc.
Do you have some other machine where to try installing ALPS? Or maybe even a virtual machine on your current system?
Best regards, Michele
-- ETH Zurich Michele Dolfi Institute for Theoretical Physics HIT G 32.4 Wolfgang-Pauli-Str. 27 8093 Zurich Switzerland
dolfim@phys.ethz.ch www.itp.phys.ethz.ch
+41 44 633 78 56 phone +41 44 633 11 15 fax
On Feb 3, 2016, at 6:18 PM, T.J.Hewitt th396@kent.ac.uk wrote:
Dear ALPS users,
I've been having issues with the stability of the DMRG program provided by ALPS (2.2.b4). The program has been crashing quite frequently. I can run maybe 3-5 simulations before the program crashes. I had no problems with the program when a started using ALPS a few months ago. Unfortunately the crash seems to also take other applications with it, in that other programs will cease to start or function properly. Such programs include dnf, Problem Reporting, logs, gedit and gnome-shell. In order to get everything working correctly a full system reboot is needed.
I can't find much in the way of error information. Problem Reporting tells me a segmentation fault occurred and the terminal output gives an std::bad_alloc error. Often a crash will cause the computer to freeze for several minutes before it starts working again. The crashes occur on simple programs, even those provided in the ALPS DMRG Tutorials.
I've tried recompiling and rebuilding ALPS from scratch but it still results in the same crashing of DMRG. I'm using a Fedora 22 system and I followed the ALPS installation instructions along with those given here https://lists.phys.ethz.ch/pipermail/comp-phys-alps-users/2013/002005.html. Although I edited a few make files so the cmake commands would correctly find the lapack and lpsolve libraries. Perhaps I missed an error or warning during the build process or there is an incompatibility between Fedora 22 and ALPS. I've tried looking through the logs and error reports to find a clue but have come up with very little. I've also had a look through the mailing list archives to see if anyone else has had an issue such as this but I was able to find anything. I can post any logs or error reports if needed.
Does anyone experienced an issue such as this or have a suggestion about it?
Thanks, Tyler Hewitt