-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
memory problem #248
Comments
an update... I removed the --zs keyword in the crest invocation and the message changed to: *** glibc detected *** xtb: corrupted double-linked list: 0x0000000007e21630 *** |
Turn out that I have been able to launch calculations placing the initial xyz file in a directory... so I guess that in my home directory there is a file that sould be deleted (and maybe I do not have permissions to do that) or some error of this kind... |
Hm I don't know how this would be related to parallelization. |
I have some problems possibly related to memory management when trying to use CREST (v2.12, with different XTB versions, both installed from binaries). Aparently, XTB works fine, but fails when it is called by CREST even for the first geometry optimization. The messages refers to memory management:
*** glibc detected *** xtb: free(): invalid next size (normal): 0x0000000007c6bc30 ***
when run with -T=1, or:
forrtl: severe (174): SIGSEGV, segmentation fault occurred
when run with -T=2
I also set: ulimit -s unlimited, exported: OMP_STACKSIZE= large amount of memory G, etc.
Funniest thing is that I have run CREST before without these issues on the same server. I think that I did not anythin "nasty" to the server... only upgraded some CUDA libraries in a different machine that shares some directories by NFS.
Any idea?
Thanks:
Luis
The text was updated successfully, but these errors were encountered: