View Issue Details

IDProjectCategoryView StatusLast Update
0003879OpenFOAMBugpublic2022-09-06 14:10
ReporterAliShaha Assigned Towill  
Status resolvedResolutionfixed 
PlatformUnixOSUbuntuOS Version20.04
Product Version10 
Fixed in Versiondev 
Summary0003879: Problem using LoadBalancer with cyclic BC

I ran into a problem running LoadBalancer with cyclic BC. After the run, running reconstructParMesh and then reconstructPar leads to the following error:

Create time

Reconstructing fields for mesh region0

Time = 1e-05s

Reconstructing FV fields

    Reconstructing volScalarFields

#0 Foam::error::printStack(Foam::Ostream&)corrupted double-linked list

Also, an extra text appears in e.g. reconstructed CN file in the above example with processorBC?

        type processor;
        patchType processorCyclic;
        value nonuniform List<scalar>

I am not sure if the laodBalancer handles the cyclic BCs correctly during the simulation in the first place. But also it seems there is an issue when the case is reconstructed.
The OpenFOAM code is updated to the latest commit (regarding AMI BC).
Steps To Reproduce- cd OpenFOAM-10/tutorials/combustion/reactingFoam/laminar/counterFlowFlame2D_GRI
- blockMeshDict: divide the outlet bc into two cyclic patches (e.g. top and bottom)
- 0.orig: update the boundary conditions
- controlDIct: set endTime 4e-5
- ./Allrun-parallel
Additional InformationI attached the modified tutorial.
TagsNo tags attached.



2022-09-05 10:40



2022-09-05 10:57

manager   ~0012722

What level of funding could you allocate to further work on dynamic load-balancing to resolve this issue?


2022-09-06 14:10

manager   ~0012724

Version 10 does not support the reconstruction of meshes with processor cyclic patches. Dev does support this. It was added in the following commit:

So, you will need to upgrade to dev if you wish to use this feature.

Also, in investigating your case, I found a further bug in the handling of redistribution of processor cyclic fields. This has been fixed here:

So, if you upgrade to dev, make sure that it is a recent enough pull to include
this commit. Otherwise you will just hit another bug.

Issue History

Date Modified Username Field Change
2022-09-05 10:40 AliShaha New Issue
2022-09-05 10:40 AliShaha File Added:
2022-09-05 10:57 henry Note Added: 0012722
2022-09-06 14:10 will Assigned To => will
2022-09-06 14:10 will Status new => resolved
2022-09-06 14:10 will Resolution open => fixed
2022-09-06 14:10 will Fixed in Version => dev
2022-09-06 14:10 will Note Added: 0012724