[ulfaslak]

Dear foamers,

I'm having big trouble with 'Segmentation fault: 11', and I'd like to know if anyone else is experiencing something similar. I've searched the forum for answers but came up empty handed so here goes:

In a nutshell: I can run my case decomposed into 8 parts, but get nasty segfaults when I try with 16 parts. Decomposition is done using the 'simple'-method. The attached runLogs show output of both the 8-procs-run and the 16-procs-run, with the included error printed by terminal.

Further info: My jobs are sent to a high performance computing center, where the vast majority of nodes has 8 processors. I thought this could have something to do with it, as decomposePar needs hosts names of all the machines that the case is distributed to if it is not run one multiprocessor machine, but what confuses me is that I've previously been able to run the exact same case on 16 processors, on that same computing center, without error.

My second thought was that decomposePar splits the mesh into even parts, cutting straight through intersecting cells, consequently creating tiny cells in the decomposed domains, which would make the Courant Number explode in those cells (Courant Number is inversely proportional to cell volume so it would essentially be like dividing by zero, hence the segfault). However, I do not expect this to be the case as inspection indicates that it preserves each cell volume.

I'm running OF 2.2.0.

Thank you,

Ulf Aslak

Attachments:
https://www.dropbox.com/s/wszvnmj4iowa60f/runLog8
https://www.dropbox.com/s/do1q0cimj19zx0m/runLog16
https://www.dropbox.com/s/sm7hop8568...composeParDict