Hi @NinaD. From what you state I would have guessed that it is a memory issue, but from your observations that does not quite seem to be the case. Also, if I understand correctly, you run each new simulation in a new process, i.e. even if Brian had some memory leak, this shouldn’t matter much since the memory would be freed every few minutes. A segmentation fault could be due to some error in Brian (or in Python/Cython, but less likely…), but I don’t quite see what would make the computer restart… And you’ve already checked the most important things that I’d have suggested. Maybe it is an issue in the bash script, e.g. it somehow spawns too many processes? Could you give some more information on how you launch the processes and what is the difference between the simulations that you run (i.e., what kind of parameters are you setting individually for each run?). And I assume all this was with the latest Brian version, i.e. 2.5.4?
Obviously it would be important to fix the issue you are seeing, but your use case also seems to be perfect for the new feature discussed here: Running multiple standalone simulations [Request for Feedback]
I will do a new Brian release later this week, and this feature will be included.