svFSIplus failed because of segmentation fault
Posted: Wed Jul 31, 2024 12:16 pm
Hi SV developers,
I tried to run a project using svFSIplus on my school's computational cluster (Ubuntu 22.04 environment), but was returned segfault although we requested 100GB of memory. The error message reads:
Signal: Segmentation fault
Signal code: Address not mapped (1)
Failing at address (nil)
[ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x14f8b0d5a520]
[ 1] svFSIplus(_Z3fftiRKSt6vectorIS_IdSaIdEESaIS1_EER6fcType+0x138)[0x55c7b87db9a8]
[ 2] svFSIplus(_ZN13read_files_ns20read_temporal_valuesERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEER6bcType+0x835)[0x55c7b8848e75]
[ 3] svFSIplus(_ZN13read_files_ns7read_bcEP10SimulationP18EquationParametersR6eqTypeP27BoundaryConditionParametersR6bcType+0x14ac)[0x55c7b885623c]
[ 4] svFSIplus(_ZN13read_files_ns7read_eqEP10SimulationP18EquationParametersR6eqType+0x67f)[0x55c7b885742f]
[ 5] svFSIplus(_ZN13read_files_ns10read_filesEP10SimulationRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x14b)[0x55c7b8857c9b]
[ 6] svFSIplus(main+0x2e5)[0x55c7b871da25]
[ 7] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x14f8b0d41d90]
[ 8] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x14f8b0d41e40]
[ 9] svFSIplus(_start+0x25)[0x55c7b8731715]
*** End of error message ***
The failed case ran on svFSI (the earlier fortran version), and worked well. The google drive link to the crashed FSI project can be found here
https://drive.google.com/drive/folders/ ... sp=sharing
To troubleshoot what caused the issue, I tried running the "pipe_RCR_3d", which worked. To ensure that the issue wasn't caused by the mesh I made, I generated a mesh using TetGen embedded in SimVascular (23.03.27 on windows) and used the input file and the flow file from pipe_RCR_3d along with my mesh to test on svFSIplus, and it worked. In both cases that worked, the mesh sizes were significantly smaller (100 KB vs 31000 KB) than the one that received segfault, so I guessed that it might be an issue with the mesh size, but am not sure. Are there any known limitations on mesh size when simulating on svFSIplus? If not, do you have any suggestions?
Thank you
I tried to run a project using svFSIplus on my school's computational cluster (Ubuntu 22.04 environment), but was returned segfault although we requested 100GB of memory. The error message reads:
Signal: Segmentation fault
Signal code: Address not mapped (1)
Failing at address (nil)
[ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x14f8b0d5a520]
[ 1] svFSIplus(_Z3fftiRKSt6vectorIS_IdSaIdEESaIS1_EER6fcType+0x138)[0x55c7b87db9a8]
[ 2] svFSIplus(_ZN13read_files_ns20read_temporal_valuesERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEER6bcType+0x835)[0x55c7b8848e75]
[ 3] svFSIplus(_ZN13read_files_ns7read_bcEP10SimulationP18EquationParametersR6eqTypeP27BoundaryConditionParametersR6bcType+0x14ac)[0x55c7b885623c]
[ 4] svFSIplus(_ZN13read_files_ns7read_eqEP10SimulationP18EquationParametersR6eqType+0x67f)[0x55c7b885742f]
[ 5] svFSIplus(_ZN13read_files_ns10read_filesEP10SimulationRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x14b)[0x55c7b8857c9b]
[ 6] svFSIplus(main+0x2e5)[0x55c7b871da25]
[ 7] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x14f8b0d41d90]
[ 8] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x14f8b0d41e40]
[ 9] svFSIplus(_start+0x25)[0x55c7b8731715]
*** End of error message ***
The failed case ran on svFSI (the earlier fortran version), and worked well. The google drive link to the crashed FSI project can be found here
https://drive.google.com/drive/folders/ ... sp=sharing
To troubleshoot what caused the issue, I tried running the "pipe_RCR_3d", which worked. To ensure that the issue wasn't caused by the mesh I made, I generated a mesh using TetGen embedded in SimVascular (23.03.27 on windows) and used the input file and the flow file from pipe_RCR_3d along with my mesh to test on svFSIplus, and it worked. In both cases that worked, the mesh sizes were significantly smaller (100 KB vs 31000 KB) than the one that received segfault, so I guessed that it might be an issue with the mesh size, but am not sure. Are there any known limitations on mesh size when simulating on svFSIplus? If not, do you have any suggestions?
Thank you