-
Notifications
You must be signed in to change notification settings - Fork 39
Description
Hello,
During some tests, running standard calculations (everything used as default), I got in trouble with the following error
double free or corruption (!prev)
Program received signal SIGABRT: Process abort signal.
Backtrace for this error:
#0 0x71bbb2623960 in ???
#1 0x71bbb2622ac5 in ???
#2 0x71bbb224251f in ???
at ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#3 0x71bbb22969fc in __pthread_kill_implementation
at ./nptl/pthread_kill.c:44
#4 0x71bbb22969fc in __pthread_kill_internal
at ./nptl/pthread_kill.c:78
#5 0x71bbb22969fc in __GI___pthread_kill
at ./nptl/pthread_kill.c:89
#6 0x71bbb2242475 in __GI_raise
at ../sysdeps/posix/raise.c:26
#7 0x71bbb22287f2 in _GI_abort
at ./stdlib/abort.c:79
#8 0x71bbb2289676 in libc_message
at ../sysdeps/posix/libc_fatal.c:156
#9 0x71bbb22a0cfb in malloc_printerr
at ./malloc/malloc.c:5664
#10 0x71bbb22a2e7b in int_free
at ./malloc/malloc.c:4591
#11 0x71bbb22a5452 in GI___libc_free
at ./malloc/malloc.c:3391
#12 0x5ba63a2a134b in bld_psi_configuration_to_psi_det
at /home/aaron/Apps/qp2/src/fci/IRPF90_temp/csf/configurations.irp.F90:1149
#13 0x5ba63a2a4974 in provide_psi_configuration_to_psi_det
at /home/aaron/Apps/qp2/src/fci/IRPF90_temp/csf/configurations.irp.F90:1076
#14 0x5ba63a2a8c4e in provide_n_csf
at /home/aaron/Apps/qp2/src/fci/IRPF90_temp/csf/csf.irp.F90:46
#15 0x5ba63a343f22 in print_summary
at /home/aaron/Apps/qp2/src/fci/IRPF90_temp/iterations/print_summary.irp.F90:76
#16 0x5ba63a28100c in run_stochastic_cipsi
at /home/aaron/Apps/qp2/src/fci/IRPF90_temp/cipsi/stochastic_cipsi.irp.F90:504
#17 0x5ba63a2623ed in fci
at /home/aaron/Apps/qp2/src/fci/IRPF90_temp/fci.irp.F90:67
#18 0x5ba63a262165 in irp_program
at /home/aaron/Apps/qp2/src/fci/IRPF90_temp/fci.irp.F90:11
#19 0x5ba63a262165 in main
at /home/aaron/Apps/qp2/src/fci/IRPF90_temp/fci.irp.F90:14
Aborted (core dumped)
Program exited with code 134.
Wall time: 0:33:31
However, I cannot determine if this error comes internally from some subroutine of QP2, or if its just my computer that cannot handle too much memory. However, is there some keyword that can help to alleviate this? I have been looking into the documentation, and I was also trying to find the source of the error, but I cannot find it.
Kind regards